Merge branch '4.x' into tv4g1-1509-sequence-fields

.github/ISSUE_TEMPLATE/bug_report.yml

@@ -0,0 +1,60 @@
+name: Bug Report
+description: Create a report to help us improve Tripal
+body:
+  - type: markdown
+    attributes:
+      value: |
+        # BUG/ERROR report
+
+        ## System Information
+        All information is available in your site's administrator report area
+        (Administration Toolbar > Reports > Status Report)
+  - type: input
+    id: tripal_version
+    attributes:
+      label: Tripal Version
+  - type: input
+    id: drupal_version
+    attributes:
+      label: Drupal Version
+  - type: input
+    id: postgresql_version
+    attributes:
+      label: PostgreSQL Version
+  - type: input
+    id: php_version
+    attributes:
+      label: PHP Version
+  - type: markdown
+    attributes:
+      value: |
+        ## Issue Description
+        Please describe your issue here. Some information you might want to include:
+          - the page you're seeing the issue on
+          - what behavior you're experiencing versus what you expect
+          - really anything you think might best help us help you!
+        For required fields that do not make sense for this issue, please enter **n/a**.
+  - type: textarea
+    id: general_issue_description
+    attributes:
+      label: General Description
+      description: A general description of the issue
+    validations:
+      required: true
+  - type: textarea
+    id: steps_to_reproduce
+    attributes:
+      label: Steps to reproduce
+      description: What steps are necessary to recreate the bug/error?  Clear instructions here will make it easier for us to fix the problem!
+  - type: textarea
+    id: error_messages
+    attributes:
+      label: Error messages
+      description: Please include any error messages you find.
+      placeholder: Pasted text is automatically formatted cleanly, no need for backticks.
+      render: shell
+  - type: textarea
+    id: screenshots
+    attributes:
+      label: Screenshots
+      description: Upload screenshots into this field, and optionally provide a description of each.

.github/ISSUE_TEMPLATE/core_development_task.yml

@@ -0,0 +1,24 @@
+name: Core Development Task
+description: For keeping track of Tripal 4 core development.
+body:
+  - type: markdown
+    attributes:
+      value: |
+        # Core Tripal 4 Development Task
+        Remember to tag this issue with 1 or more groups that it relates to.
+
+        I suggest using the "Development Branch" section to the right once you create the issue.
+        This links the branch to the issue and will automatically close the issue when the PR is merged.
+  - type: textarea
+    id: task_description
+    attributes:
+      label: Task Description
+      description: Describe the core development task.
+    validations:
+        required: true
+  - type: input
+    id: branch_name
+    attributes:
+      label: Branch Name
+      description: Fill this in after submitting this issue and opening a new branch.
+      value: tv4g[0-9]-issue\d+-[optional short descriptor]

.github/ISSUE_TEMPLATE/discussion_question.yml

@@ -0,0 +1,20 @@
+name: Discussion / Question
+description: Discuss a topic / Ask for help.
+body:
+  - type: markdown
+    attributes:
+      value: |
+        # Instructions
+        Our intent is to use Github as an open forum to help community members connect.
+        If you are looking to do any of the following, you are in the right place! and Thank You!
+          - Ask for help/documentation/clarification of Tripal Functionality and Site Building/Management
+          - Discuss controlled vocabulary terms for your data
+          - Ask for input on site/module design questions
+          - State your intent to develop a specific extension module
+          - Really any type of discussion or question -we want to hear from you!
+  - type: textarea
+    id: discussion_question
+    attributes:
+      label: Discussion or Question
+    validations:
+        required: true

.github/ISSUE_TEMPLATE/tripal_4_feature_request.yml

@@ -0,0 +1,55 @@
+name: Tripal 4 Feature Request
+description: Suggest an idea for this project
+body:
+  - type: markdown
+    attributes: 
+      value: |
+        # Tripal 4 Feature Request
+        ## Instructions
+        The following template is meant to structure your feature request.
+        Please keep in mind, this issue may evolve into discussion for an extension module if it's decided that the feature is not a good fit for Tripal Core.
+
+        Go over all the following points, and select the options that best apply to you.
+  - type: dropdown
+    id: existing_problem
+    attributes:
+      label: This feature attempts to solve an existing problem
+      options:
+        - "Yes"
+        - "No"
+  - type: dropdown
+    id: open_to_develop_or_collab_extensino
+    attributes:
+      label: I am open to developing or collaborating on an extension module if this is not a good fit for Tripal Core
+      description: No pressure here, just good to know upfront :-)
+      options:
+        - "Yes"
+        - "No"
+  - type: dropdown
+    id: urgency
+    attributes:
+      label: Is this feature urgent?
+      options:
+        - "Yes"
+        - "No"
+  - type: textarea
+    id: description
+    attributes:
+      label: Description
+      description: A clear and conccise description of what you want to happen.
+  - type: textarea
+    id: use-case
+    attributes:
+      label: Your specific use case
+      description: Please describe how you would use this feature in your own Tripal site and why you need it.
+  - type: textarea
+    id: generally_applicable
+    attributes:
+      label: Generally Applicable
+      description: Why do you feel this is generally applicable? 
+      placeholder: Suggest other use cases if possible.
+  - type: textarea
+    id: additional_information_screenshots
+    attributes:
+      label: Additional information/screenshots
+      description: Add any other context or screenshots about the feature request here.

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,26 @@
+<!--- Thank you for contributing! -->
+<!--- Provide a general summary of your changes in the Title above -->
+<!--- See our Contribution Guidelines here:
+          https://tripaldoc.readthedocs.io/en/latest/contributing.html -->
+
+
+<!---  Please set the header below based on the PR type:
+# New Feature
+# Bug Fix
+# Tripal 4 Core Dev Task  --->
+
+#
+
+### Issue #
+
+<!--- Enter the Tripal version this PR applies to (i.e. either 3 or 4 ;-p) --->
+### Tripal Version: 
+
+## Description
+<!--- Describe your changes in detail -->
+<!--- Why is this change required? What problem does it solve? -->
+
+## Testing?
+<!--- Please describe in detail how to test these changes. -->
+<!--- Reviewers will use this section to test the submission! -->
+<!--- If you've implemented PHPUnit tests, you can describe the test cases here. -->