feat(ci): proactively detect submodule-pin drift + maintainer parity - #16
Merged
Merged
Conversation
Fundamental hardening against the submodule pin-drift failure class (members' squash-merges orphan the commit the hub pinned, eventually breaking the membership-integrity gate with 'not our ref'): - anchor-drift.yml: add a weekly 'schedule' + 'workflow_dispatch' so pin drift surfaces proactively, not only when someone happens to push. - anchor-drift.yml: add a non-failing advisory step that warns, per member, when a pin is BEHIND its main tip — the early-warning precursor state, caught before the pin is fully orphaned. 'continue-on-error' keeps the gate green; every member declares branch=main so the comparison is exact. Also adds the 'Maintain governance parity' section to QUICKSTART-MAINTAINER.adoc, for parity with the a2ml hub (a2ml already carried it; this was the one structural gap between the two maintainer quickstarts). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01RXXRgbGB2G5oGLJg1CS29T
hyperpolymath
marked this pull request as ready for review
June 27, 2026 19:26
|
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
2 participants
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.
Summary
Fundamental, in-scope hardening against the submodule pin-drift failure class — the root cause of the
membership-integrityfailures this hub hit earlier. When a member repo squash-merges, the commit the hub pinned is orphaned; the gate then fails hard withupload-pack: not our ref(fixed reactively in #13 by re-pinning). This makes the hub detect drift before it becomes fatal and on a schedule rather than only on push. Also closes a small maintainer-doc parity gap.Changes
.github/workflows/anchor-drift.ymlschedule(cron: '17 6 * * 1') andworkflow_dispatch. Themembership-integritypin-resolution gate now runs even when nobody pushes.continue-on-error: true) step compares each member's pinned commit to its currentmaintip and emits a::warning::for any pin that is behind — the precursor state, caught before the pin is fully orphaned. Every member declaresbranch = main, so the comparison is exact.QUICKSTART-MAINTAINER.adoc== Maintain governance paritysection for parity with the a2ml hub (a2ml already carried it; this was the one structural gap between the two maintainer quickstarts).Why this is safe
continue-on-errormeans the advisory step can never turnmembership-integrityred; the existing hard pin-resolution still gates correctness..a2mlfiles touched → strict governance gate is unchanged.dash-clean; workflow re-parses as valid YAML.Scope note
The source of drift is in the member repos and outside this hub. A self-healing variant (scheduled job opening a re-pin PR) needs
pull-requests: writeplus the org's "Allow Actions to create PRs" setting — left as an opt-in next step in #14.Refs #14, #7.
🤖 Generated with Claude Code
Generated by Claude Code