Skip to content

Verify every public repository, not the four the page named - #3

Merged
ftymoshchuk merged 1 commit into
mainfrom
claude/eloquent-ptolemy-dsy07a
Sep 29, 2026
Merged

ftymoshchuk merged 1 commit into
mainfrom
claude/eloquent-ptolemy-dsy07a

Conversation

@ftymoshchuk

Copy link
Copy Markdown
Member

The Verify loop in docs/new-repository.md named four repositories: sigrix-mcp, mullion, postern and actions. Meanwhile sigrix-launcher, bailey and gatehouse were 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 --jq pattern the page already uses. It leaves out .github, and the page explains why: that repo runs no CI, so a ruleset requiring ci-passed would 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_history rule that actions has. The old table would have flagged it as drift once the loop reached actions.

  • The ci-passed section no longer lists repositories by name. Every public repository with CI has the job except postern, which the page already explains.

  • "The rest of a new repository" now covers:

    • a JavaScript package (gatehouse): checkout and setup-node pinned directly, since there's no Node action here; the vitest pin guard; npm trusted publishing with the first version published by hand;
    • the fork guard and the rule that a release is never cancelled, which every release workflow now has.

    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.md line under Unreleased. This is documentation only; neither action changes.

How it was checked

  • Every claim about the other repositories was read from their current main: which ones have a ci-passed job, which releases have the fork guard and never-cancel setting, and everything sigrix-mcp carries. The rules in force were read from each repo's rules/branches/main.
  • The Verify block ran as written, pulled straight from the markdown, through a small stand-in for gh api that uses curl and jq. That covered all eight public repos and confirms the quoting and the loop work. Five print healthy output matching the Expect table, including actions' extra rule and postern's two checks. sigrix-launcher, bailey and gatehouse print [] in every field.
  • One gap: the session this was written from can't call the org-wide orgs/sigrix-io/repos endpoint. So the new list filter was run over the real repository objects from repos/sigrix-io/<repo>, which have the same name, visibility and archived fields. It kept exactly the eight public repos and dropped private sigrix, a .github stand-in and an archived stand-in. The first real run of gh api orgs/sigrix-io/repos will be an org admin's.

Still open (settings, not this PR)

Until someone applies docs/default-branch.ruleset.json to sigrix-launcher, bailey and gatehouse, this page's Verify loop will show all three as unprotected. Each of them already reports a passing ci-passed on main.

🤖 Generated with Claude Code

https://claude.ai/code/session_01DpQHLFQaQN2SXqGUz3zZso


Generated by Claude Code

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
@ftymoshchuk
ftymoshchuk merged commit 1816509 into main Sep 29, 2026
7 checks passed
@ftymoshchuk
ftymoshchuk deleted the claude/eloquent-ptolemy-dsy07a branch September 29, 2026 18:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants