docs: make the umbrella canonical for triage labels and integration-branch lifecycle - #7
Merged
Merged
Conversation
…ranch lifecycle Two vocabularies were canonical by accident in threadbase-mobile, which is the failure this repo's issue-tracker doc exists to prevent. Adds triage-labels.md for the state labels — needs-triage, needs-info, ready-for-agent, ready-for-human — with their colours and the rule that they are additive to priority, type and area rather than a substitute. Both threadbase-mobile and threadbase-streamer now carry the identical five-label set. Adds integration-branch-lifecycle.md for the rule the integration-branch skill in both repos operates under: an integration branch is a staging area with an expiry, a run ends when the branch is gone, and each ref is audited by whether it holds a file main has never had rather than by ancestry. Squash-merging gives landed content a new SHA, so ancestry reports every merged pull request as unlanded. The mobile retirement document is not moved here: its refs, file counts and misnamed commit are that repo's history, and three of its relative links do not resolve outside it. This file states the reusable rule and links to that record as its origin. Indexes both in docs/README.md and cross-links the triage set from issue-tracker.md.
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.
Two vocabularies were canonical by accident in
threadbase-mobile— which is the exact failuredocs/issue-tracker.mdexists to prevent:docs/triage-labels.mdThe state labels —
needs-triage,needs-info,ready-for-agent,ready-for-human,wontfix— with their colours, and the rule that they are additive to priority/type/area rather than a substitute.Includes the two near-collisions worth naming (
questionthe type versusneeds-infothe state;wontfixserving both roles) and a compliance query for issues carrying two states at once.Both component repos now hold the identical five-label set at identical colours, verified after this was filed.
docs/integration-branch-lifecycle.mdThe rule the
integration-branchskill in both repos operates under: an integration branch is a staging area with an expiry, a run ends when the branch is gone rather than when it is green, and never develop on it.Carries the audit that makes deletion safe — ask does this ref hold a file
mainhas never had, not "is it merged", because squash-merging gives landed content a new SHA and ancestry therefore reports every merged pull request as unlanded.Plus the two checks from that audit that return a confident wrong answer instead of an error: a branch-name glob is a filter rather than an inventory, and non-ancestry does not mean unlanded.
What is deliberately not moved here
threadbase-mobile/docs/integration-branch-retirement-2026-08-12.mdstays in that repo.Its ref list, file counts and misnamed-commit analysis are that repo's history, and three of its relative links resolve only there.
The new lifecycle doc states the reusable rule and links to that record as its origin.
Reference
Documentation only.