Skip to content

ci: Version-control GitHub labels via labels.yml - #311

Merged
scouten-adobe merged 3 commits into
mainfrom
sync-github-labels
Sep 10, 2026
Merged

ci: Version-control GitHub labels via labels.yml#311
scouten-adobe merged 3 commits into
mainfrom
sync-github-labels

Conversation

@scouten-adobe

Copy link
Copy Markdown
Collaborator

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 to main, or workflow_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) and canary (cross-repo canary drift detection -- no extracted crates here). 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.

Requested to land ahead of #310, which references several of these labels.

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

codecov Bot commented Sep 9, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 72.16%. Comparing base (978c933) to head (0a7663d).

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.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@scouten-adobe
scouten-adobe marked this pull request as ready for review September 9, 2026 23:36
@scouten-adobe
scouten-adobe enabled auto-merge (squash) September 9, 2026 23:48
@scouten-adobe
scouten-adobe merged commit f432f2a into main Sep 10, 2026
17 checks passed
@scouten-adobe
scouten-adobe deleted the sync-github-labels branch September 10, 2026 22:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant