templates: org-default issue + PR templates - #6
Merged
Conversation
Inheritable org defaults so every QAtlasHub repo gets consistent forms without a per-repo copy: - PULL_REQUEST_TEMPLATE.md — Description / Type-of-Change (label checkboxes) / **Proposed Changes** / **Usage or Results** / checklist. The two named sections are the PR's changelog contribution: build_release_notes.py extracts them into the published GitHub Release notes (the rich release-notes system). - ISSUE_TEMPLATE/bug_report.yml (🐛), wishlist.yml (💭), config.yml (blank issues on; repo-specific Discussions link dropped for the org default).
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
1 participant
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.
Inheritable org-default issue & PR templates so every QAtlasHub repo gets consistent forms without shipping its own copy.
PULL_REQUEST_TEMPLATE.md— Description / Type-of-Change (label checkboxes that drive version-resolver & categories) / Proposed Changes / Usage or Results / checklist. The two named sections are the PR's changelog contribution —build_release_notes.pyextracts them into the published Release notes (the rich release-notes system this is coupled to).ISSUE_TEMPLATE/—bug_report.yml(🐛),wishlist.yml(💭 with priority/rationale/sketch/refs),config.yml(blank issues enabled; the per-repo Discussions link is dropped for the org default).Inheritance is all-or-nothing per repo: a repo with its own
ISSUE_TEMPLATE/keeps it; repos without one now inherit these. Follow-up (coupled): standardise the rich release-notes system (build_release_notes.py+PublishRelease) org-wide and kill the TagBot/release-drafter duplication that produces the doubled## Changelog/ oversized index.