From febad85674d4437b15843e9075de7ee00e00d40b Mon Sep 17 00:00:00 2001
From: John Clema <john.clema@gmail.com>
Date: Thu, 19 Dec 2024 13:13:27 +0800
Subject: [PATCH 1/4] chore: Add comprehensive pull request template

- Add structured sections for change type and testing
- Include container-specific environment details
- Add checklist for quality assurance
- Support documentation and container image updates
---
 .github/PULL_REQUEST_TEMPLATE.md | 33 ++++++++++++++++++++++++++++++++
 1 file changed, 33 insertions(+)
 create mode 100644 .github/PULL_REQUEST_TEMPLATE.md

diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md
new file mode 100644
index 0000000..d837e4a
--- /dev/null
+++ b/.github/PULL_REQUEST_TEMPLATE.md
@@ -0,0 +1,33 @@
+# Description
+
+<!-- Provide a clear and concise description of your changes -->
+
+## Type of change
+
+<!-- Please check the relevant option(s) -->
+
+- [ ] Bug fix (non-breaking change which fixes an issue)
+- [ ] New feature (non-breaking change which adds functionality)
+- [ ] Documentation update
+- [ ] Container image update
+- [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
+- [ ] Other (please specify)
+
+## Testing
+
+<!-- Describe the tests you ran and how -->
+
+- [ ] Built container locally
+- [ ] Tested container functionality
+- [ ] Verified documentation accuracy
+- [ ] Other (please specify):
+
+### Test Environment Details
+
+- OS:
+- Docker/Podman version:
+- Singularity/Apptainer version (if applicable):
+
+## Related Issues
+
+<!-- Add related github issues or PRs -->

From 8585be84310bb643aab4f03843c918c84d3d5a26 Mon Sep 17 00:00:00 2001
From: John Clema <john.clema@gmail.com>
Date: Thu, 19 Dec 2024 13:13:54 +0800
Subject: [PATCH 2/4] chore: Add bug report issue template

- Include container environment specifications
- Add structured reproduction steps
- Include error output section with formatting
- Add fields for container image and command details
---
 .github/ISSUE_TEMPLATE/bug_report.md | 51 ++++++++++++++++++++++++++++
 1 file changed, 51 insertions(+)
 create mode 100644 .github/ISSUE_TEMPLATE/bug_report.md

diff --git a/.github/ISSUE_TEMPLATE/bug_report.md b/.github/ISSUE_TEMPLATE/bug_report.md
new file mode 100644
index 0000000..2cdb9ea
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/bug_report.md
@@ -0,0 +1,51 @@
+---
+name: Bug Report
+about: Create a report to help us improve
+title: "[BUG] "
+labels: bug
+assignees: ""
+---
+
+## Describe the Bug
+
+<!-- A clear and concise description of what the bug is -->
+
+## To Reproduce
+
+Steps to reproduce the behavior:
+
+1.
+2.
+3.
+
+## Expected Behavior
+
+<!-- A clear and concise description of what you expected to happen -->
+
+## Environment
+
+- OS:
+- Docker/Podman version:
+- Singularity/Apptainer version (if applicable):
+- Container image and tag:
+- Command used:
+
+## Error Output
+
+<!-- If applicable, add error messages or logs -->
+
+```
+[Error output here]
+```
+
+## Screenshots
+
+<!-- If applicable, add screenshots to help explain your problem -->
+
+## Additional Context
+
+<!-- Add any other context about the problem here -->
+
+## Possible Solution
+
+<!-- If you have suggestions on a fix for the bug, please describe them here -->

From 73526e37d4175de9b44a553509e4872ef8542232 Mon Sep 17 00:00:00 2001
From: John Clema <john.clema@gmail.com>
Date: Thu, 19 Dec 2024 13:14:15 +0800
Subject: [PATCH 3/4] chore: Add documentation issue template

- Add location specification field
- Include current vs proposed changes sections
- Add documentation-specific checklist
- Support improvement suggestions
---
 .github/ISSUE_TEMPLATE/documentation.md | 33 +++++++++++++++++++++++++
 1 file changed, 33 insertions(+)
 create mode 100644 .github/ISSUE_TEMPLATE/documentation.md

diff --git a/.github/ISSUE_TEMPLATE/documentation.md b/.github/ISSUE_TEMPLATE/documentation.md
new file mode 100644
index 0000000..e86f61e
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/documentation.md
@@ -0,0 +1,33 @@
+---
+name: Documentation
+about: Report issues with documentation or suggest improvements
+title: "[DOCS] "
+labels: documentation
+assignees: ""
+---
+
+## Documentation Location
+
+<!-- Specify where the documentation issue is (README, specific file, etc.) -->
+
+## Current Documentation
+
+<!-- What does the current documentation say? -->
+
+## Issue/Suggested Improvement
+
+<!-- Describe what's wrong or what could be improved -->
+
+## Proposed Changes
+
+<!-- If you have specific wording suggestions, include them here -->
+
+## Additional Context
+
+<!-- Add any other context about the documentation issue here -->
+
+## Checklist
+
+- [ ] I have checked that this is not already documented elsewhere
+- [ ] I have checked for related issues
+- [ ] I have suggested specific improvements where possible

From 2d961ef98d6a075cb0e37a3e48f33725025d5016 Mon Sep 17 00:00:00 2001
From: John Clema <john.clema@gmail.com>
Date: Thu, 19 Dec 2024 13:14:33 +0800
Subject: [PATCH 4/4] chore: Add feature request issue template

- Add problem description section
- Include use case documentation
- Add impact assessment section
- Include implementation suggestions field
---
 .github/ISSUE_TEMPLATE/feature_request.md | 35 +++++++++++++++++++++++
 1 file changed, 35 insertions(+)
 create mode 100644 .github/ISSUE_TEMPLATE/feature_request.md

diff --git a/.github/ISSUE_TEMPLATE/feature_request.md b/.github/ISSUE_TEMPLATE/feature_request.md
new file mode 100644
index 0000000..72658b7
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/feature_request.md
@@ -0,0 +1,35 @@
+---
+name: Feature Request
+about: Suggest an idea for this project
+title: "[FEATURE] "
+labels: enhancement
+assignees: ""
+---
+
+## Is your feature request related to a problem?
+
+<!-- A clear and concise description of what the problem is. Ex. I'm always frustrated when [...] -->
+
+## Describe the solution you'd like
+
+<!-- A clear and concise description of what you want to happen -->
+
+## Describe alternatives you've considered
+
+<!-- A clear and concise description of any alternative solutions or features you've considered -->
+
+## Use Case
+
+<!-- Describe the use case for this feature -->
+
+## Additional Context
+
+<!-- Add any other context, screenshots, or examples about the feature request here -->
+
+## Impact on Existing Functionality
+
+<!-- Describe any potential impact this feature might have on existing functionality -->
+
+## Implementation Ideas
+
+<!-- If you have any ideas about how to implement this feature, please share them here -->