chore: normalize GitHub label taxonomy - #28
Merged
Conversation
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.
Why
RunSift currently has two overlapping label systems, including spaced and unspaced names, duplicate priorities, generic areas, and
status:*labels that conflict with GitHub Project status.Changes
.github/labels.json.status:*labels so Project Status remains the source of truth.Canonical groups
type:*priority:*size:*area:*flag:*labelsValidation
The workflow creates or updates canonical labels, migrates existing issue labels, and then removes obsolete aliases.
Rollback
Revert this PR and restore any required labels from Git history. The migration is declarative and idempotent, so the configuration can be adjusted and rerun safely.