vrr/codeburn
2
0
Fork 0
mirror of https://github.com/AgentSeal/codeburn.git synced 2026-10-20 11:44:39 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

Require screenshots on UI pull requests (#1437)

Browse source 
* Require before/after screenshots on UI pull requests

* Split UI screenshot checkbox into not-a-UI-change and UI-change alternatives
This commit is contained in:
Resham Joshi 2026-09-15 21:13:20 +02:00 • committed by GitHub
parent 21c677a450
commit 94090583f0
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
2 changed files with 4 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

4
.github/PULL_REQUEST_TEMPLATE.md vendored
View file

@ -2,11 +2,13 @@
<!-- What does this PR do? 1-3 bullet points. -->
## Testing
## Testing / Verification
- [ ] I have tested this locally against real data (not just unit tests)
- [ ] `npm test` passes
- [ ] `npm run build` succeeds
- [ ] Not a UI change
- [ ] UI change: before and after screenshots attached below
### For new providers only:

1
CONTRIBUTING.md
View file

@ -132,6 +132,7 @@ PRs that add a provider based solely on online documentation or AI-generated cod
6. Fill in the description. A PR whose "Summary" is still the template is closed automatically; write what the change does and why, then reopen.
7. If this is your first contribution and the change is over about 300 lines, open an issue first and reference it in the PR. Large work gets discussed before it is written; small fixes do not need this.
8. Keep at most five pull requests open at a time. A sixth is closed automatically with a note and can be reopened once one of the others lands or closes. If you have more ideas than open slots, file an issue for each so the work is visible and can be discussed before it is written.
9. UI change? Attach before and after screenshots of the affected screen to the PR. No screenshots, no review.
## Reporting Bugs