chore: require PRs to link an issue or discussion#2093
Merged
Conversation
- Add PR template with required linked issue/discussion section - Add check-linked-issue CI job that validates PR body contains a reference (#123, Closes/Fixes/Relates, GitHub URL, or CF-# ticket) - Wire into required-checks-passed gate so it blocks merge - Update CONTRIBUTING.md with the policy and motivation
github-actions
Bot
added
the
workflow-modified
This was referenced Apr 23, 2026
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.
Closes #2079 (partial — infrastructure improvement)
Summary
.github/PULL_REQUEST_TEMPLATE.md) with a required "Linked issue or discussion" sectioncheck-linked-issueCI job that validates the PR body contains an issue/discussion reference — blocks merge via therequired-checks-passedgateCONTRIBUTING.mdwith the policy and motivation: have a conversation before the code so contributors get direction early and implementations fit the project's needsTest plan
check-linked-issueCloses #123in the body — CI should pass