ci: Version-control GitHub labels via labels.yml - #311
Merged
Conversation
Ports c2pa-rs's label-sync mechanism (.github/labels.yml + the sync workflow, via crazy-max/ghaction-github-labeler) so the labels the release process depends on (release, backport-stable, release-train, upstream-first-verified, reconciliation, check-release) are version- controlled instead of hand-created in the UI -- this is the automated alternative to manually clicking through label creation, which the release-infra PR's checklist otherwise called for. Dropped two labels that reference infrastructure c2patool doesn't have: - 'safe to test': superseded by GitHub's native fork-PR-approval setting (see ci.yml's own header comment -- this repo never adopted the older label-based trust mechanism to begin with). - 'canary': for the cross-repo canary workflow (drift detection against extracted crates like c2pa_cbor), which doesn't apply here -- c2patool has no extracted crates of its own. Adjusted 'release'/'check-release' descriptions to reference c2patool's actual suites (Tier 1A / beta-preflight) instead of c2pa-rs's Tier 1A+1B+2. Kept the general triage labels (bug, feature, task, status: *) for consistency with upstream's taxonomy. Lands ahead of the release-infrastructure PR, which references several of these labels.
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #311 +/- ##
=======================================
Coverage 72.16% 72.16%
=======================================
Files 4 4
Lines 1060 1060
=======================================
Hits 765 765
Misses 295 295 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
scouten-adobe
marked this pull request as ready for review
September 9, 2026 23:36
scouten-adobe
enabled auto-merge (squash)
September 9, 2026 23:48
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.
Ports c2pa-rs's label-sync mechanism so the labels the release process depends on (
release,backport-stable,release-train,upstream-first-verified,reconciliation,check-release) are version-controlled instead of hand-created in the UI. Once merged and this workflow runs (push tomain, orworkflow_dispatch), it creates/updates those labels automatically -- replacing the manual label-creation step previously called out in #310's checklist.Dropped two labels that reference infrastructure c2patool doesn't have:
safe to test(superseded by GitHub's native fork-PR-approval, which this repo already uses) andcanary(cross-repo canary drift detection -- no extracted crates here). Adjustedrelease/check-releasedescriptions to reference c2patool's actual suites (Tier 1A / beta-preflight) instead of c2pa-rs's Tier 1A+1B+2. Kept the general triage labels (bug, feature, task, status: *) for consistency with upstream.Requested to land ahead of #310, which references several of these labels.