Repository navigation
Document the single-maintainer setup for the knowledge gate - #226
Conversation
The owner decided that no second knowledge maintainer will be added. The
CODEOWNERS comment and the feature doc's cutover steps now say so.
- The human-approved path covers PRs opened by others; the service's own PRs
that go to people are closed or amended and re-gated.
- The rules are split in two, so the owner's code-owner bypass never
bypasses kb-gate:
- main-gate, with no bypass: merge queue, kb-gate required from GitHub
Actions, no deletion or force push;
- main-code-owners, with the owner as the only bypass: pull request,
code-owner review, dismiss stale approvals.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 028280953e
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| # own changes here go through the owner's bypass of the code-owner ruleset | ||
| # (see doc/features/knowledge-service.md), never through kb-gate's. |
There was a problem hiding this comment.
When @tzhouam authors a change under .github/**, this newly documented bypass allows it to merge without a Code Owner approval, directly contradicting lines 3–5, which still claim that no such change can land without a maintainer approving the current head. Because this comment describes the gate's security guarantees, update that earlier statement to acknowledge the single-maintainer bypass.
Useful? React with 👍 / 👎.
The owner decided not to add a second knowledge maintainer, so
CODEOWNERSand the cutover steps are updated to match.kb-gate:main-gate, no bypass: merge queue,kb-gaterequired from GitHub Actions, no deletion or force push;main-code-owners, owner is the only bypass: pull request, code-owner review, dismiss stale approvals.Docs and comments only. The commit hook approved it.
🤖 Generated with Claude Code