Skip to content

docs: add a Risk section to the PR template #37101

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
brennanb2025 merged 2 commits into from
Nov 1, 2026
Merged

docs: add a Risk section to the PR template #37101

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
c06bd87
docs: add a Risk section to the PR template
brennanb2025 Nov 1, 2026
4b6f169
docs: keep the change to the PR template
brennanb2025 Nov 1, 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
7 changes: 7 additions & 0 deletions .github/pull_request_template.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -31,6 +31,12 @@ Fixes #
- [ ] I manually tested these changes locally
- [ ] Automated tests added/updated, or explained why not below

## Risk

<!-- What could this break, and for whom? Name the riskiest part of the change and what users would see if it went wrong. Call out anything that crosses a boundary: saved data or settings, older paired phones or SSH servers, other platforms, agents, or performance. Say how to back it out: a plain revert, or what a revert would not undo. -->

**Level:** <!-- Low, Medium, or High -->

## AI Disclosure

<!-- DO NOT FILL IN IF YOU ARE STABLYAI TEAM MEMBER (INTERNAL CONTRIBUTOR), IGNORE SECTION: -->
Expand All @@ -50,6 +56,7 @@ Ensure no issues in: Security, Cross-platform support (Linux, Windows, Mac), Rem

- [ ] This PR is small and focused
- [ ] I explained what changed and why (ELI5, the user-facing before/after, the mechanism, and why over the alternatives)
- [ ] I stated the risk: what could break, for whom, and how to back it out
- [ ] Before/after screenshots or videos attached for UI changes, or `N/A` with reason
- [ ] Self-reviewed for correctness, security, and performance
- [ ] Cross-platform, SSH/remote, and path/shortcut impact considered (or N/A)
Expand Down
Loading