chore: add org label sync workflow - #192
Open
beatrizmcouto wants to merge 1 commit into
Open
Conversation
Add a label policy, sync script, and manual workflow to standardize labels across complytime repositories while preserving repo-specific labels. Co-authored-by: Cursor <cursoragent@cursor.com>
beatrizmcouto
requested review from
jpower432 and
marcusburghardt
as code owners
July 29, 2026 09:00
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.
Summary
labels-policy.jsonto define standard labels, rename-only migrations, local-only labels to preserve, and labels to deletescripts/sync_labels.pyto apply the policy repo by repoREADME.mdandMAINTAINING.mdBehavior
The workflow targets all complytime repositories except
complytime/complytimeandroadmap.It supports three behaviors at once:
60 days,clean up,docker,llm_assisted,question,to validate, andto validadeAssumptions
private-sprint-sub-issueis treated as preserve, not delete, because it appeared in the keep-list and the existing live label uses that casingdockeris renamed tocontainerquestion,to validate, andto validadeare consolidated intovalidateRelated Issues
N/A
Review Hints
labels-policy.jsonfirst; it is the source of truth for the requested label changesworkflow_dispatch) so it can be dry-run safely before any org-wide applyGenerated with Cursor assistance