Adopt the shared label sync - #134
Merged
Merged
Conversation
Call the reusable label-sync workflow from magicsunday/.github so this repository's labels follow the canonical manifest. The sync is non-destructive (skip-delete), so repository-specific labels are preserved.
|
Caution The consumer version of Gemini Code Assist on GitHub has been sunset. All code review activity has officially ceased. |
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.
Adopt the shared label sync for this repository.
label-sync.ymlfrommagicsunday/.github, so the label set follows the canonical manifest instead of drifting per repository.workflow_dispatch, and apushtrigger scoped to this workflow file so a change to it applies immediately.issues: writebecause a reusable workflow'sGITHUB_TOKENis capped by the caller's permission ceiling — a job-level grant inside the called workflow alone would not survive the move.concurrencygroup (withoutcancel-in-progress) serialises runs so an overlapping schedule/dispatch/push cannot drive two concurrent label mutations, and no in-flight sync is cancelled mid-write.