docs: say that a model reviews every pull request - #4
Open
akf66 wants to merge 1 commit into
Open
Conversation
The review workflow landed in the previous commit but nothing told a contributor it exists. Finding out that P2 blocks your merge by watching a check go red is a bad first experience, and the reason it blocks — a nit is cheapest to fix before anyone else reads the diff — is not guessable from the check name. Also states the part a reviewer bot usually leaves unsaid: a wrong finding should be answered in the thread, not silently merged past. An unanswered finding and an unread one look the same from the outside. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
5 tasks
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.
Documents the review gate that landed in
ci: review pull requests with OrcaCode Review.Nothing currently tells a contributor the reviewer exists. Finding out that P2 blocks your merge by watching a check go red is a bad first experience, and the reason it blocks isn't guessable from the check name.
This is also the first PR opened after the workflow reached the base branch, so it doubles as the trigger test.