feat: add GitHub issue and PR templates (#651)#699
Open
MAN7A-afk wants to merge 1 commit into
Open
Conversation
|
@MAN7A-afk Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits. You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Closes #651
Adds GitHub issue and PR templates to standardize contributions and reduce back-and-forth during review.
Changes
bug_report.md
— guides reporters through description, steps to reproduce, expected vs actual behavior, and environment details
feature_request.md
— prompts contributors for motivation, proposed solution, alternatives considered, and acceptance criteria
PULL_REQUEST_TEMPLATE.md
— pre-populates PRs with a type-of-change selector, testing notes, and a checklist covering lint, tests, docs, secrets, and branch status
Type of Change
Documentation update / CI configuration
Checklist
✅ No code logic changed
✅ No tests required
✅ Templates follow GitHub's expected file paths and front-matter format