Repository navigation
Verify every public repository, not the four the page named - #3
Merged
Merged
Conversation
The Verify loop in docs/new-repository.md named sigrix-mcp, mullion, postern and actions. sigrix-launcher, bailey and gatehouse were public with no ruleset at all while it did, and the loop could not have shown it: a typed list only checks the repositories someone remembered to add. It now reads the org's public, unarchived repositories from the API. .github is left out, and the page says why: it runs no CI, so a ruleset requiring ci-passed would hold every pull request there. Alongside that: - "When something is off" says what Verify prints for a branch with no ruleset (every field []), and how to confirm nothing protects it. - The Expect table allows the required_linear_history rule actions carries, which the loop now reaches. - The ci-passed section no longer lists repositories: every public one with CI has the job except postern. - "The rest of a new repository" covers a JavaScript package (gatehouse: checkout and setup-node pinned directly, the vitest pin guard, npm trusted publishing with a hand-published first version), and the fork guard and no-cancel rule every release workflow now carries. Documentation only; neither action changes. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DpQHLFQaQN2SXqGUz3zZso
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.
The Verify loop in
docs/new-repository.mdnamed four repositories:sigrix-mcp,mullion,posternandactions. Meanwhilesigrix-launcher,baileyandgatehousewere public with no ruleset at all, and the loop couldn't have shown it, because a typed list only checks the repositories someone remembered to add. The loop now gets the list from the org: every public repository that isn't archived.Changes
Verify builds its repository list from
gh api orgs/sigrix-io/repos --paginate, filtered with the same--jqpattern the page already uses. It leaves out.github, and the page explains why: that repo runs no CI, so a ruleset requiringci-passedwould block every pull request there."When something is off" gets a new row for what Verify prints when a branch has no ruleset (every field
[], and no ruleset listed under it). It also shows how to confirm nothing protects the branch (branches/main --jq .protected→false).Expect table: it now allows the extra
required_linear_historyrule thatactionshas. The old table would have flagged it as drift once the loop reachedactions.The
ci-passedsection no longer lists repositories by name. Every public repository with CI has the job exceptpostern, which the page already explains."The rest of a new repository" now covers:
gatehouse):checkoutandsetup-nodepinned directly, since there's no Node action here; the vitest pin guard; npm trusted publishing with the first version published by hand;It also says why to copy from
sigrix-mcp: it has every file that section lists. "The most recently aligned" no longer holds.A
CHANGELOG.mdline under Unreleased. This is documentation only; neither action changes.How it was checked
main: which ones have aci-passedjob, which releases have the fork guard and never-cancel setting, and everythingsigrix-mcpcarries. The rules in force were read from each repo'srules/branches/main.gh apithat usescurlandjq. That covered all eight public repos and confirms the quoting and the loop work. Five print healthy output matching the Expect table, includingactions' extra rule andpostern's two checks.sigrix-launcher,baileyandgatehouseprint[]in every field.orgs/sigrix-io/reposendpoint. So the new list filter was run over the real repository objects fromrepos/sigrix-io/<repo>, which have the samename,visibilityandarchivedfields. It kept exactly the eight public repos and dropped privatesigrix, a.githubstand-in and an archived stand-in. The first real run ofgh api orgs/sigrix-io/reposwill be an org admin's.Still open (settings, not this PR)
Until someone applies
docs/default-branch.ruleset.jsontosigrix-launcher,baileyandgatehouse, this page's Verify loop will show all three as unprotected. Each of them already reports a passingci-passedonmain.🤖 Generated with Claude Code
https://claude.ai/code/session_01DpQHLFQaQN2SXqGUz3zZso
Generated by Claude Code