ci: fail when a citation into the threadbase umbrella stops resolving - #799
Merged
Conversation
Canonical conventions now live in the umbrella repo and this repo cites them as plain URLs. A rename there breaks every citation here silently, because nothing in a markdown file 404-checks itself and no pull request in this repo is involved. Adds a workflow that resolves every https://github.com/RonenMars/threadbase/blob/main/ link found in the tree, on pull requests touching markdown and on a weekly schedule. The schedule is the half that matters: the break arrives from the other repo. An empty match set fails rather than passes, because zero links means the matcher stopped matching, not that the citations are healthy. Cites the new lifecycle document from both copies of the integration-branch skill, in the expiry section and beside the ref audit it describes. The retirement document stays here, since the history is this repo's, and the lifecycle document links back to it as the origin of the rule.
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
1 participant
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.
Canonical conventions now live in the umbrella repo and this repo cites them as plain URLs — the "A" half of the approach agreed in #796.
A URL has exactly one real weakness: a rename in the umbrella breaks every citation here silently.
Nothing in a markdown file 404-checks itself, and no pull request in this repo is involved when it happens.
The check
Resolves every
https://github.com/RonenMars/threadbase/blob/main/…link in the tree, on pull requests touching markdown and weekly on a schedule — the schedule is the half that matters, since the break arrives from the other repo.An empty match set fails rather than passes. Zero links means the matcher stopped matching, not that the citations are healthy.
Verified in all three directions before landing: three real links resolve, a fabricated path returns 404 and fails the job, and a tree with no umbrella links fails loudly.
Skill citations
Both copies of the
integration-branchskill —.claude/and.agents/, kept byte-identical — now citeintegration-branch-lifecycle.mdin the expiry section and beside the ref audit whose script it holds.docs/integration-branch-retirement-2026-08-12.mdstays here — the refs, file counts and misnamed-commit analysis are this repo's history, and three of its relative links resolve only here. The lifecycle document links back to it as the origin of the rule.Reference: #796, RonenMars/threadbase#6, RonenMars/threadbase-streamer#663.