Repository navigation
docs: main is ruleset-locked, and signed commits are what is blocking every open PR - #68
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Lin1er
force-pushed
the
docs/main-ruleset-signed-commits
branch
from
September 28, 2026 13:45
dd0f727 to
475e72a
Compare
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.
Lin1er
force-pushed
the
docs/main-ruleset-signed-commits
branch
from
September 28, 2026 13:49
475e72a to
4ba7929
Compare
This branch was successfully deployed
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.
Every open PR in this repo is
BLOCKEDright now, and not for the reason #66 suggests.A repository ruleset named
masterwas created on the default branch today at 19:20 (+07): no direct push, no force-push, no delete, PR required, andrequired_signatures. Itsbypass_actorslist is empty andcurrent_user_can_bypassisnever, sogh pr merge --admindoes not help.install + lint + buildSUCCESS,landing install + lint + buildSUCCESSunsignedunsignedunknown_keySo the diagnosis in #66 — a required check whose workflow is path-filtered and therefore never reports — is not what is happening.
install + lint + buildreports SUCCESS on both of @Nabil-Aufa's PRs, and the ruleset carries norequired_status_checksrule 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
git rebase -f -S origin/main,git push --force-with-lease). Every member has to do the setup once.unknown_keymeans the signature is fine but the public key is not registered as a Signing Key — an authentication key does not count.required_signaturesfrom 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.mdonly, 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.This PR is itself signed, so it will show
unknown_keyuntil the key is registered — it is subject to exactly the rule it documents.cc @axel @fable @Nabil-Aufa @Ancung