Bram-Hub · charlestian23 · Jul 26, 2022 · Jul 26, 2022 · Jul 26, 2022 · Jul 26, 2022
diff --git a/.github/ISSUE_TEMPLATE/bug_report.yml b/.github/ISSUE_TEMPLATE/bug_report.yml
@@ -0,0  1,55 @@
 name: Bug report
 description: Create a report to help us improve
 title: "[BUG] <description>"
 labels: [bug]
 body:
   - type: textarea
     id: description
     attributes:
       label: "Description"
       description: "A clear and concise description of what the bug is."
       placeholder: "If your issue relates to a particular puzzle, make sure to remember to add the corresponding label to the issue."
     validations:
       required: true
   - type: textarea
     id: reproduce
     attributes:
       label: "Steps to Reproduce"
       description: "Steps to reproduce the behavior:"
       placeholder: "1. Go to '...'
 
         2. Click on '....'
 
         3. See error"
     validations:
       required: true
   - type: textarea
     id: expected_behavior
     attributes:
       label: "Expected Behavior"
       description: "A clear and concise description of what you expected to happen."
     validations:
       required: true
   - type: textarea
     id: screenshot
     attributes:
       label: "Screenshots"
       description: "If applicable, add screenshots to help explain your problem."
       placeholder: "![DESCRIPTION](LINK.png)"
     validations:
       required: false
   - type: textarea
     id: files
     attributes:
       label: "Puzzle Files"
       description: "If applicable, add any puzzle files to help explain your problem."
       placeholder: You will need to zip up the puzzle files before you can attach them to your issue.
     validations:
       required: false
   - type: textarea
     id: additional_context
     attributes:
       label: "Additional Context"
       description: "Add any other context about the problem here."
     validations:
       required: false
diff --git a/.github/ISSUE_TEMPLATE/feature_request.yml b/.github/ISSUE_TEMPLATE/feature_request.yml
@@ -0,0  1,34 @@
 name: Feature request
 description: Suggest an idea for this project
 title: "[FEATURE] <description>"
 labels: [enhancement, new feature]
 body:
   - type: textarea
     id: description
     attributes:
       label: "Is your feature request related to a problem? Please describe."
       description: "A clear and concise description of what the problem is."
       placeholder: "Ex. I'm always frustrated when [...]"
     validations:
       required: true
   - type: textarea
     id: solution
     attributes:
       label: "Describe the solution you'd like"
       description: "A clear and concise description of what you want to happen."
     validations:
       required: true
   - type: textarea
     id: alternatives
     attributes:
       label: "Describe alternatives you've considered"
       description: "A clear and concise description of any alternative solutions or features you've considered."
     validations:
       required: false
   - type: textarea
     id: additional_context
     attributes:
       label: "Additional Context"
       description: "Add any other context or screenshots about the feature request here."
     validations:
       required: false
diff --git a/.github/PULL_REQUEST_TEMPLATE/pull_request_template.md b/.github/PULL_REQUEST_TEMPLATE/pull_request_template.md
@@ -0,0  1,26 @@
 # Description
 
 <!-- Please include a summary of the changes and the related issue. Please also include relevant motivation and context. List any dependencies that are required for this change. -->
 
 <!-- If your pull request is not related to a particular issue, delete the statement below. -->
 Closes #(issue) 
 
 ## Type of change
 
 - [ ] Bug fix (non-breaking change which fixes an issue)
 - [ ] New feature (non-breaking change which adds functionality)
 - [ ] Enhancement (improvement to an already existing feature)
 - [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
 
 # How Has This Been Tested?
 
 <!-- Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration. -->
 
 # Checklist:
 
 - [ ] I have performed a self-review of my code
 - [ ] I have commented my code, particularly in hard-to-understand areas
 - [ ] I have made corresponding changes to the documentation (if applicable)
 - [ ] My changes generate no new warnings
 - [ ] I have added tests that prove my fix is effective or that my feature works
 - [ ] New and existing unit tests pass locally with my changes