ci: enable automatic label sync triggers - #106
Merged
Merged
Conversation
Step 6 of the onboarding order in dexpace/.github labels/README.md. The first real sync has been read and applied, so the automatic triggers can come on. The Monday cron is the part that matters. Between dispatches a label edited in the web UI stays edited; the cron is what re-heals it. Without it the YAML in dexpace/.github is advisory rather than authoritative. Merging this fires a pruning sync immediately: the push trigger matches this path, and LABELS_PRUNE is set on this repo. That is a no-op today because the repo already converged — 42 labels present, adapters and v1/MVP already gone, javascript excluded — so the merge doubles as a reconciliation check.
fuad-daoud
approved these changes
Sep 9, 2026
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
2 participants
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.
Step 6 of onboarding, the last one. Uncomments the
pushandscheduletriggers left off in #105.
Why the cron matters
It is the only thing that re-heals a label edited in the web UI. Between
dispatches, a hand-edited color or description just stays edited, and the YAML
in
dexpace/.githubquietly becomes advisory rather than authoritative.Pruning is what makes the files the source of truth; the cron is what makes
pruning happen without anyone remembering.
Merging this runs a real pruning sync
Worth stating plainly: the
pushtrigger matches this exact path, andLABELS_PRUNE=trueis set on this repo, so the merge commit triggers a syncwith pruning live — not a dry run.
That is safe because the repo has already converged, verified after the
manual sequence:
common,docs,package,sdk, plusjavascriptadapters,v1/MVPv1/MVPSo the expected result of this merge is a run that creates nothing, updates
nothing and deletes nothing. If it does anything at all, something drifted
between now and the merge, and the run log will say what.