Skip to content

chore: ask in the PR template whether a change is breaking #3782

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
armando-navarro merged 2 commits into from
Oct 5, 2026
Merged

chore: ask in the PR template whether a change is breaking #3782

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
7d3afe9
chore: ask in the PR template whether a change is breaking
armando-navarro Oct 1, 2026
7e7c443
Merge branch 'main' into f1-pr-template-breaking-change
armando-navarro Oct 5, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions PULL_REQUEST_TEMPLATE.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -25,6 +25,7 @@ before sending PRs. We cannot accept code without this.
- Issue number for this PR: #nnn (required)
- Docs included?: (yes/no; required for all API/functional changes)
- Test units included?: (yes/no; required)
- Breaking change?: (yes/no, required. If yes, add a `BREAKING CHANGE:` footer to your commit message that says what an upgrading app must change, and put `!` before the colon in the PR title and the commit subject, like `fix(auth)!: ...`)
- In a clean directory, `yarn install`, `yarn test` run successfully? (yes/no; required)

### Description
Expand Down
Loading