Repository navigation
Prepare contributor docs and PR-only repository governance - #14
Merged
Merged
Conversation
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.
AccessLab's contributor docs mixed the implementation session's push authorization with repository policy, and
maincurrently has no enforced protection. Contributors now have a fork/topic-branch PR workflow, review and validation expectations, a Code of Conduct, CODEOWNERS, feature proposal form, and expanded PR template. The task helper rejects main/detached HEAD and leaves its branch pending if PR creation fails, instead of pushing directly to main.The reviewed
.github/main-protection.jsonrequires PRs, one code-owner approval, up-to-dateverify, resolved conversations, administrator enforcement, and no force pushes/deletion.docs/repository-governance.mdprovides free built-in GitHub settings and fork-CI safety guidance. Protection is not yet active: the integration's apply request returned HTTP 403Resource not accessible by integration; the repository owner must apply the documented settings. CODEOWNERS is routing, not enforcement. Maintainer-authored PRs will need another eligible code owner once protection is activated.Validation:
pnpm lint,git diff --check, local Markdown links, protection JSON assertions, Python syntax, and a main-branch rejection rehearsal passed. Existing PR CI runs the full suite. No dependency or workflow changes; CI retains SHA-pinned official actions on standard Linux runners, with no paid action/service added.