Repository navigation
docs: ask for visuals in pull requests - #8
Merged
Merged
Conversation
🐕 Shuni ReviewNo new issues found. 🤖 Model: Review scope: Full review Reviewed files (2)
🐕 Review complete — View session on Shuni Portal 🐾 🤖 Model: |
omercnet
enabled auto-merge (squash)
November 21, 2026 10:17
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
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.
What changed
The pull request template gets a "Visuals" section, and CONTRIBUTING.md gets the same rule in a few sentences: features show screenshots or a short recording (plus a diagram or terminal capture where helpful), bug fixes show before and after shots, and "not applicable" needs a reason.
Why
Reviewers should see what changed, not only read it.
How it was verified
Reading the rendered template; no code changes.
Visuals
Not applicable: documentation-only change.
Checklist