Repository navigation
Allow review by any eligible invited team member - #3
Merged
Merged
Conversation
This was referenced Oct 16, 2026
ABZerra
marked this pull request as ready for review
October 16, 2026 16:51
ABZerra
disabled auto-merge
October 16, 2026 16:51
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.
Replace the designated primary/backup approval rule with one independent approval from any invited repository team member whose invitation is accepted and whose effective GitHub permissions permit required-review approval (write or higher under standard roles). Authors still cannot approve their own PRs.
Owner request: ABZerra explicitly requested that anyone invited to the repository team may approve a change, replacing the approver-and-backup requirement. Scope: review policy and its setup documentation; no changes to validators or workflows. Remove the fixed CODEOWNERS roster and update shared instructions, contribution guidance, README and setup.
With the owner's explicit authorization to apply the live change before this PR is reviewed or merged, native settings now set
require_code_owner_reviewsto false while keeping one required approval, stale-approval dismissal, administrator enforcement, strict branch freshness, the three Actions-bound checks, and no bypass/force push/deletion. Verify actual collaborator permissions, including inherited grants, match the intended team. Read-only access or an unaccepted invitation cannot satisfy GitHub's native required-review rule.This PR stays draft with auto-merge off under the owner's instruction not to merge or bypass review. Live protection readback confirms only the designated code-owner requirement changed; one independent approval and all other protections remain enforced. The old CODEOWNERS file on main no longer restricts eligible approvals. This PR removes that obsolete roster and updates published documentation after independent review. No self-approval, bypass, or merge was performed.
Validation: all three local validators passed with zero violations;
git diff --checkpassed. Documentation/governance-only change; validator and workflow implementations are unchanged.Human review handoff
Review this governance change first. PR #5 includes this governance commit to resolve the README overlap, while also targeting main as required by the trusted validator. Its description links the Cowork-only comparison for focused review. Review this PR first; do not merge #5 ahead of it. PR #3 still targets main and its reviewed head is unchanged.
The owner requested human-review preparation but prohibited merging. This PR therefore remains draft with auto-merge off: the existing ready-for-review workflow would automatically enable auto-merge for a non-draft PR targeting main. Review and comments are welcome; no human approval is claimed. Do not mark ready or enable auto-merge until publication is separately authorized.
Reviewer focus: invited collaborators with accepted write-or-higher access may approve another person's change; one independent approval and all three required checks remain required; no primary/backup roster is retained. Independent AI review found no actionable issues. Live setting application was separately owner-authorized and verified. No additional settings changes are proposed here.
One-time owner publication exception
ABZerra explicitly authorized merging PRs #3 and #5 without the usual independent human approval for initial sharing readiness. This supersedes the earlier draft/no-merge instruction for these two PRs only. No human review approval is claimed. Required review policy remains in force for all future changes; any temporary administrative exception must be restored and verified after each merge. Checks must pass on the final content.