heavy-duty/ceremony
7
0
Fork 2
Code Issues 1 Pull requests Projects Releases 8 Packages Wiki Activity Actions

docs: make consumer labels tag-aware

Browse source
This commit is contained in:
codex-bot-andresmgsl 2026-07-23 16:09:42 +00:00
parent 162ce6b817
commit 0d74c827e7
1 changed files with 11 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

11
docs/CONSUMERS.md
View file

@ -251,6 +251,7 @@ on:
workflow_dispatch: # bootstraps missing labels on a fresh repo workflow_dispatch: # bootstraps missing labels on a fresh repo
pull_request_target: pull_request_target:
types: [opened, reopened, ready_for_review, converted_to_draft, synchronize, labeled, unlabeled] types: [opened, reopened, ready_for_review, converted_to_draft, synchronize, labeled, unlabeled]
# Unreleased — not in 0.1.0; add only with the first tag carrying ceremony#32.
issues: issues:
types: [opened, labeled, unlabeled, assigned, unassigned, closed] types: [opened, labeled, unlabeled, assigned, unassigned, closed]
permissions: permissions:
@ -262,6 +263,10 @@ jobs:
uses: heavy-duty/ceremony/.github/workflows/labels.yml@<pinned-tag> uses: heavy-duty/ceremony/.github/workflows/labels.yml@<pinned-tag>
``` ```
The `issues:` trigger is **unreleased** and is not in `0.1.0`. A consumer
pinned to `0.1.0` omits it. Add it only when bumping every ceremony reference
to the first tag carrying ceremony#32; never mix refs to adopt it early.
`pull_request_target` is intentional: fork PRs need the base repository's `pull_request_target` is intentional: fork PRs need the base repository's
token to write labels. The reusable workflow executes no PR code. It checks token to write labels. The reusable workflow executes no PR code. It checks
out only the consumer's base branch and the pinned ceremony implementation. out only the consumer's base branch and the pinned ceremony implementation.
@ -278,6 +283,12 @@ scope:cli|C5DEF5|The command-line surface
scope:docs|C5DEF5|Documentation scope:docs|C5DEF5|Documentation
``` ```
The mandatory `triage-actors=` setting is also **unreleased** and is not
accepted by `0.1.0`. At that tag the file contains `panel=` plus scope rows
only; adding `triage-actors=` is a parse failure, not an ignored setting. Add
it at the same pin bump as the `issues:` trigger, to the first tag carrying
ceremony#32 — never before it and never through mixed refs.
Both actor lists are whitespace-separated. `triage-actors` names the identities Both actor lists are whitespace-separated. `triage-actors` names the identities
allowed to mint issues without the sweep applying `needs-triage`. Label rows use exactly allowed to mint issues without the sweep applying `needs-triage`. Label rows use exactly
`name|color|description`; blank lines are ignored and extra pipes are refused. `name|color|description`; blank lines are ignored and extra pipes are refused.