Skip to content

docs: main is ruleset-locked, and signed commits are what is blocking every open PR - #68

Merged
Lin1er merged 1 commit into
mainfrom
docs/main-ruleset-signed-commits
Sep 28, 2026
Merged

Lin1er merged 1 commit into
mainfrom
docs/main-ruleset-signed-commits

Conversation

@Lin1er

@Lin1er Lin1er commented Sep 28, 2026

Copy link
Copy Markdown
Owner

Every open PR in this repo is BLOCKED right now, and not for the reason #66 suggests.

A repository ruleset named master was created on the default branch today at 19:20 (+07): no direct push, no force-push, no delete, PR required, and required_signatures. Its bypass_actors list is empty and current_user_can_bypass is never, so gh pr merge --admin does not help.

PR CI Commits Why blocked
#66 install + lint + build SUCCESS, landing install + lint + build SUCCESS unsigned signature
#63 SUCCESS unsigned signature
#67 SUCCESS unknown_key signing key not registered on the account

So the diagnosis in #66 — a required check whose workflow is path-filtered and therefore never reports — is not what is happening. install + lint + build reports SUCCESS on both of @Nabil-Aufa's PRs, and the ruleset carries no required_status_checks rule at all. A docs-only PR is not a special case; it is the same signature rule.

Two ways out, and it is @axel's and the repo owner's call, not a code change

  1. Everyone registers a signing key. Then old commits get re-signed (git rebase -f -S origin/main, git push --force-with-lease). Every member has to do the setup once. unknown_key means the signature is fine but the public key is not registered as a Signing Key — an authentication key does not count.
  2. Drop required_signatures from the ruleset (or add bypass actors) at https://github.com/Lin1er/sterish/rules/24116073, and merge as before.

If the ruleset was not created deliberately, option 2 is the right one. I have not touched the setting: it is repo security configuration, so it should be a decision, not a side effect of unblocking myself.

What this PR contains

CLAUDE.md only, 22 lines: the rules, the local signing config this worktree now carries, how to read the two failure modes apart, and the two options above — so the next PR does not rediscover this from scratch.

gh api repos/Lin1er/sterish/pulls/<n>/commits \
  --jq '.[] | {sha: .sha[0:8], verified: .commit.verification.verified, reason: .commit.verification.reason}'

This PR is itself signed, so it will show unknown_key until the key is registered — it is subject to exactly the rule it documents.

cc @axel @fable @Nabil-Aufa @Ancung

@vercel

vercel Bot commented Sep 28, 2026 •

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
sterish Ready Ready Preview Sep 28, 2026 1:46pm UTC

For about ninety minutes today no PR in this repo could be merged, with green CI
on all of them. Worth recording, because the symptoms point away from the cause
and the first two diagnoses were both wrong.

Not a path-filtered required check that never reports, as #66 suggested:
`install + lint + build` was SUCCESS on both of Nabil's PRs and the ruleset
carried no `required_status_checks` rule at all. Not `required_signatures`
either — that rule was removed at 20:05 and all three PRs stayed BLOCKED.

It was the `update` rule, "Restrict updates". Merging a PR updates the ref, so it
blocks merges and not only direct pushes, and with an empty bypass list an admin
merge cannot get around it. GitHub reports `mergeable: MERGEABLE` next to
`mergeStateStatus: BLOCKED` and names no rule in the error.

The ruleset has since been deleted, so this is written as the recipe for next
time: how to read the effective rules, which combination protects main without
freezing it, and why the fix has to come from the web UI — the gh OAuth token is
answered 404 for the rulesets API even though the account is a repository admin.

This branch was successfully deployed

1 active deployment
Preview — 4ba7929b Deployed Sep 28, 2026 by vercel[bot]
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.

1 participant