Skip to content

Commit 9eeb3e2

Browse files
lippytmlippytm
authored
Merge pull request #18 from lippytm/copilot/fix-70376a2e-7ffa-488d-9c8e-6d74f6ea9240
2 parents f7f89d1 + 9664fbb commit 9eeb3e2

File tree

9 files changed

+584
-0
lines changed

9 files changed

+584
-0
lines changed

‎.github/ISSUE_TEMPLATE/bug_report.yml‎

Lines changed: 73 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,73 @@
1+
name: Bug Report
2+
description: File a bug report to help us improve
3+
title: "[Bug]: "
4+
labels: ["bug", "triage"]
5+
assignees: []
6+
7+
body:
8+
- type: markdown
9+
attributes:
10+
value: |
11+
Thanks for taking the time to fill out this bug report!
12+
13+
- type: textarea
14+
id: what-happened
15+
attributes:
16+
label: What happened?
17+
description: Also tell us, what did you expect to happen?
18+
placeholder: A clear and concise description of what the bug is.
19+
validations:
20+
required: true
21+
22+
- type: textarea
23+
id: steps-to-reproduce
24+
attributes:
25+
label: Steps to Reproduce
26+
description: Steps to reproduce the behavior
27+
placeholder: |
28+
1. Go to '...'
29+
2. Click on '....'
30+
3. Scroll down to '....'
31+
4. See error
32+
validations:
33+
required: true
34+
35+
- type: textarea
36+
id: expected-behavior
37+
attributes:
38+
label: Expected Behavior
39+
description: A clear and concise description of what you expected to happen.
40+
validations:
41+
required: true
42+
43+
- type: textarea
44+
id: screenshots
45+
attributes:
46+
label: Screenshots
47+
description: If applicable, add screenshots to help explain your problem.
48+
49+
- type: textarea
50+
id: environment
51+
attributes:
52+
label: Environment
53+
description: Please provide your environment information
54+
placeholder: |
55+
- OS: [e.g. iOS]
56+
- Browser [e.g. chrome, safari]
57+
- Version [e.g. 22]
58+
- Node.js version: [e.g. 18.0.0]
59+
60+
- type: textarea
61+
id: additional-context
62+
attributes:
63+
label: Additional Context
64+
description: Add any other context about the problem here.
65+
66+
- type: checkboxes
67+
id: terms
68+
attributes:
69+
label: Code of Conduct
70+
description: By submitting this issue, you agree to follow our Code of Conduct
71+
options:
72+
- label: I agree to follow this project's Code of Conduct
73+
required: true

‎.github/ISSUE_TEMPLATE/config.yml‎

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,8 @@
1+
blank_issues_enabled: false
2+
contact_links:
3+
- name: 💬 GitHub Discussions
4+
url: https://github.com/lippytm/AI-Time-Machines/discussions
5+
about: Ask questions and discuss with the community
6+
- name: 🛡️ Security Issues
7+
url: https://github.com/lippytm/AI-Time-Machines/security/advisories/new
8+
about: Report security vulnerabilities privately

‎.github/ISSUE_TEMPLATE/documentation.yml‎

Lines changed: 72 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,72 @@
1+
name: Documentation Issue
2+
description: Report an issue with documentation
3+
title: "[Docs]: "
4+
labels: ["documentation"]
5+
assignees: []
6+
7+
body:
8+
- type: markdown
9+
attributes:
10+
value: |
11+
Thank you for helping improve our documentation!
12+
13+
- type: dropdown
14+
id: documentation-type
15+
attributes:
16+
label: Documentation Type
17+
description: What type of documentation issue is this?
18+
options:
19+
- Missing documentation
20+
- Incorrect information
21+
- Unclear explanation
22+
- Broken links
23+
- Typos/grammar
24+
- Outdated information
25+
- Formatting issues
26+
- Other
27+
validations:
28+
required: true
29+
30+
- type: textarea
31+
id: location
32+
attributes:
33+
label: Location
34+
description: Where is the documentation issue located?
35+
placeholder: |
36+
- File: README.md
37+
- Section: Installation
38+
- Line number: 25
39+
- URL: https://...
40+
validations:
41+
required: true
42+
43+
- type: textarea
44+
id: issue-description
45+
attributes:
46+
label: Issue Description
47+
description: Describe the documentation issue
48+
placeholder: A clear description of what's wrong with the documentation.
49+
validations:
50+
required: true
51+
52+
- type: textarea
53+
id: suggested-fix
54+
attributes:
55+
label: Suggested Fix
56+
description: If you have a suggestion for how to fix this, please describe it
57+
placeholder: What should the documentation say instead?
58+
59+
- type: textarea
60+
id: additional-context
61+
attributes:
62+
label: Additional Context
63+
description: Add any other context about the documentation issue here.
64+
65+
- type: checkboxes
66+
id: terms
67+
attributes:
68+
label: Code of Conduct
69+
description: By submitting this issue, you agree to follow our Code of Conduct
70+
options:
71+
- label: I agree to follow this project's Code of Conduct
72+
required: true

‎.github/ISSUE_TEMPLATE/feature_request.yml‎

Lines changed: 81 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,81 @@
1+
name: Feature Request
2+
description: Suggest an idea for this project
3+
title: "[Feature]: "
4+
labels: ["enhancement", "feature-request"]
5+
assignees: []
6+
7+
body:
8+
- type: markdown
9+
attributes:
10+
value: |
11+
Thanks for suggesting a new feature! Please fill out the form below.
12+
13+
- type: textarea
14+
id: problem-description
15+
attributes:
16+
label: Problem Description
17+
description: Is your feature request related to a problem? Please describe.
18+
placeholder: A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
19+
validations:
20+
required: true
21+
22+
- type: textarea
23+
id: solution-description
24+
attributes:
25+
label: Proposed Solution
26+
description: Describe the solution you'd like
27+
placeholder: A clear and concise description of what you want to happen.
28+
validations:
29+
required: true
30+
31+
- type: textarea
32+
id: alternatives
33+
attributes:
34+
label: Alternatives Considered
35+
description: Describe alternatives you've considered
36+
placeholder: A clear and concise description of any alternative solutions or features you've considered.
37+
38+
- type: dropdown
39+
id: feature-type
40+
attributes:
41+
label: Feature Type
42+
description: What type of feature is this?
43+
options:
44+
- New functionality
45+
- Enhancement to existing feature
46+
- Performance improvement
47+
- User experience improvement
48+
- Developer experience improvement
49+
- Documentation improvement
50+
- Other
51+
validations:
52+
required: true
53+
54+
- type: dropdown
55+
id: priority
56+
attributes:
57+
label: Priority
58+
description: How important is this feature to you?
59+
options:
60+
- Critical
61+
- High
62+
- Medium
63+
- Low
64+
- Nice to have
65+
validations:
66+
required: true
67+
68+
- type: textarea
69+
id: additional-context
70+
attributes:
71+
label: Additional Context
72+
description: Add any other context or screenshots about the feature request here.
73+
74+
- type: checkboxes
75+
id: terms
76+
attributes:
77+
label: Code of Conduct
78+
description: By submitting this issue, you agree to follow our Code of Conduct
79+
options:
80+
- label: I agree to follow this project's Code of Conduct
81+
required: true

‎.github/PULL_REQUEST_TEMPLATE/pull_request_template.md‎

Lines changed: 65 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,65 @@
1+
## Description
2+
3+
<!-- Provide a brief description of the changes in this PR -->
4+
5+
## Type of Change
6+
7+
Please delete options that are not relevant.
8+
9+
- [ ] 🐛 Bug fix (non-breaking change which fixes an issue)
10+
- [ ] ✨ New feature (non-breaking change which adds functionality)
11+
- [ ] 💥 Breaking change (fix or feature that would cause existing functionality to not work as expected)
12+
- [ ] 📚 Documentation update
13+
- [ ] 🔧 Refactor (no functional changes)
14+
- [ ] ⚡ Performance improvement
15+
- [ ] 🧪 Test updates
16+
- [ ] 🔨 Build/CI updates
17+
18+
## Related Issue(s)
19+
20+
<!-- Link to the issue(s) this PR addresses -->
21+
Fixes #(issue_number)
22+
23+
## Changes Made
24+
25+
<!-- Describe the changes made in this PR -->
26+
-
27+
-
28+
-
29+
30+
## Testing
31+
32+
<!-- Describe the testing you've done -->
33+
- [ ] Unit tests pass
34+
- [ ] Integration tests pass
35+
- [ ] Manual testing completed
36+
- [ ] No breaking changes
37+
38+
## Screenshots (if applicable)
39+
40+
<!-- Add screenshots to help explain your changes -->
41+
42+
## Checklist
43+
44+
- [ ] My code follows the code style of this project
45+
- [ ] I have performed a self-review of my own code
46+
- [ ] I have commented my code, particularly in hard-to-understand areas
47+
- [ ] I have made corresponding changes to the documentation
48+
- [ ] My changes generate no new warnings
49+
- [ ] I have added tests that prove my fix is effective or that my feature works
50+
- [ ] New and existing unit tests pass locally with my changes
51+
- [ ] Any dependent changes have been merged and published
52+
53+
## Additional Context
54+
55+
<!-- Add any other context about the PR here -->
56+
57+
---
58+
59+
<!--
60+
Before submitting your PR:
61+
1. Make sure all tests pass
62+
2. Update documentation if needed
63+
3. Follow the project's coding standards
64+
4. Keep your PR focused and atomic
65+
-->

0 commit comments

Comments
 (0)