Repository navigation
ci: adopt the org label vocabulary - #105
Merged
Merged
Conversation
Calls the reusable workflow in dexpace/.github with the four profiles this repo takes: common, docs, package, sdk — 42 labels. Dispatch-only for now, and dry_run defaults on. Nothing syncs on this commit. The rename pass in labels/MIGRATION.md has to run before any sync creates the new names, or 'gh label edit bug --name type:bug' fails on the taken name and the 121 existing label assignments in this repo cannot be carried over. The push and schedule triggers are enabled once the first real sync has been read.
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.
Adds this repo's caller for the reusable label sync in
dexpace/.github, with the four profilesthis repo takes —
common,docs,package,sdk, 42 labels.This PR syncs nothing
The caller is dispatch-only and
dry_rundefaults on. Merging it does nottouch a single label. The
pushandscheduletriggers are commented out andget enabled after the first real sync has been read.
That is deliberate: a caller that synced on its own merge commit would create
type:bugbefore the rename pass could claim the name, and the migration thatpreserves issue assignments would no longer be available.
The migration already ran
Done before this PR, because renames must precede any sync:
adapters->area:transport@dexpace/rx—ASYNC-*/SEAM-*, which the normative table maps toarea:transportv1/MVP-> milestonebug(16 items),core(26),documentation(7),resilience(8) and therest kept every issue they were on. Nothing was delete-and-recreated.
What is left for the first sync
adapters(now 0 items) andv1/MVP(superseded by milestone Phase 0: Toolchain & Style Gate (scaffold milestone) #1).javascriptis protected. It is Dependabot's ecosystem label, it getsrecreated whenever deleted, and it varies per repo — so it lives in the
workflow's
excludelist rather than incommon.yml.dependenciesisidentical everywhere and is declared normally.
After merge
Per
labels/README.md, deletion is opt-in per repository:dry_runon. Read the plan.dry_runoff. The 39 labels are created.LABELS_PRUNE=true, dispatch withpruneon. The 2strays go.
pushandscheduletriggers. Without the Monday cron alabel edited in the web UI stays edited and the YAML becomes advisory.