Request @anilbeyazoglu on every pull request - #7
Merged
Conversation
Team ownership alone let a review land with whichever team member the round-robin picked. Name @anilbeyazoglu as an owner on every path so every pull request requests his review, and say so in CONTRIBUTING.md. The teams stay as co-owners, so their approval still satisfies the requirement when he is unavailable. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01K4JoCqrnJ47MqzHk9PsZ33
github-actions
Bot
added
the
external-contributor
|
Thanks for the pull request! Docyrus Open IDE is public to read and install, but while the project settles we See CONTRIBUTING.md for the current policy. |
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.
What changed
.github/CODEOWNERSnow names @anilbeyazoglu as an owner on every path, alongside the existing teams. Every pull request will request his review automatically.CONTRIBUTING.md says so, so contributors know who the review is waiting on.
What did not change, and why
The
mainruleset is untouched: 1 approving review, code-owner review required.GitHub cannot exempt a pull request's author from review requirements — bypass is actor-based, not author-based. I tested adding a named-user bypass actor to the ruleset and the API rejected it (
HTTP 404onactor_type: "User"); I confirmed afterwards that the ruleset was left intact.You already have what you asked for through the OrganizationAdmin bypass that's been on the ruleset since it was created: your own PRs merge via the bypass confirmation rather than waiting for someone else's approval. That's how you merged #1 and #5.
Two consequences worth knowing:
Because you are now a code owner on every path, GitHub will not request a review on your own PRs (it never requests review from the author), so nothing new blocks you.
How I verified it
GET /codeowners/errorsreports 0 errors on the current file; will re-check after merge, since that endpoint reads the default branch🤖 Generated with Claude Code
https://claude.ai/code/session_01K4JoCqrnJ47MqzHk9PsZ33