heavy-duty/rig
7
0
Fork 1
Code Issues 10 Pull requests Projects Releases 3 Packages Wiki Activity Actions

Ceremony on Forgejo — align actors and bootstrap the issue-flow taxonomy #116

New issue
Closed
opened 2026-07-29 15:09:04 +00:00 by codex-bot-andresmgsl · 1 comment
codex-bot-andresmgsl commented 2026-07-29 15:09:04 +00:00
Member
Copy link

Context

Ceremony automation cannot currently describe this Forgejo accurately:

  • .github/labels.conf names GitHub-era panel identities (*-bot-andresmgsl) and triage-actors=dan-claude-bot, while reviews here are submitted by *-reviewer-andresmgsl.
  • The Forgejo repository is missing core issue-flow labels including needs-triage, ready, claimed, epic, needs-ruling, attention, and offsite.
  • The labels workflow has never run on this instance because no runner is attached, so issue #111 has no queue state and PR !114's state had to be managed by hand.

Created under @andres's explicit exception in !114 comment 3664 to file the missing Ceremony-support work directly.

Spec

Make the pinned Ceremony labels workflow authoritative on Forgejo: configure the actual reviewer/triage identities, bootstrap the complete taxonomy idempotently, and prove issue/PR reconciliation with disposable test items or existing non-destructive events.

Do not hand-invent label semantics or fork the vendored .ceremony/ doctrine. Identity changes belong in rig's .github/labels.conf; taxonomy comes from the pinned Ceremony workflow.

Tasks

  • Confirm the intended Forgejo panel and triage actor usernames with @andres.
  • Update panel= and triage-actors= in .github/labels.conf to those exact accounts.
  • Run the pinned labels bootstrap after the repository runner issue is complete.
  • Verify every core label from .ceremony/LABELS.md exists with the expected description/color.
  • Exercise issue queue reconciliation and PR state/blocker reconciliation.
  • Document how Forgejo dispatches the bootstrap/sweep and any platform-specific difference from GitHub.

Acceptance criteria

  • panel= resolves to the accounts that actually review Forgejo PRs; author exclusion produces the correct required set.
  • triage-actors= resolves to the account(s) authorized to normalize issues.
  • Core labels include needs-triage, ready, claimed, blocked, epic, needs-ruling, attention, offsite, every state:*, and every blocker:* named by the pinned doctrine.
  • A new direct issue receives/retains a valid issue-flow state and malformed queue combinations are reported or repaired per Ceremony.
  • A draft PR, an active review round, an addressing round, and a fully approved current head reconcile to the documented state labels.
  • Re-running bootstrap is idempotent and preserves hand-set intent/scope labels.

Test plan

  • Run the pinned labels bootstrap and work-queue sweep twice.
  • Compare the Forgejo labels API to .ceremony/LABELS.md and .github/labels.conf.
  • Drive representative issue/PR events and inspect label timelines plus workflow logs.
  • Confirm !114's configured panel would be Claude/Kimi/Codex minus its Grok author at its current head.

Dependencies

Blocked by #115.

## Context Ceremony automation cannot currently describe this Forgejo accurately: - `.github/labels.conf` names GitHub-era panel identities (`*-bot-andresmgsl`) and `triage-actors=dan-claude-bot`, while reviews here are submitted by `*-reviewer-andresmgsl`. - The Forgejo repository is missing core issue-flow labels including `needs-triage`, `ready`, `claimed`, `epic`, `needs-ruling`, `attention`, and `offsite`. - The labels workflow has never run on this instance because no runner is attached, so issue #111 has no queue state and PR !114's state had to be managed by hand. Created under @andres's explicit exception in !114 comment 3664 to file the missing Ceremony-support work directly. ## Spec Make the pinned Ceremony labels workflow authoritative on Forgejo: configure the actual reviewer/triage identities, bootstrap the complete taxonomy idempotently, and prove issue/PR reconciliation with disposable test items or existing non-destructive events. Do not hand-invent label semantics or fork the vendored `.ceremony/` doctrine. Identity changes belong in rig's `.github/labels.conf`; taxonomy comes from the pinned Ceremony workflow. ## Tasks - [ ] Confirm the intended Forgejo panel and triage actor usernames with @andres. - [ ] Update `panel=` and `triage-actors=` in `.github/labels.conf` to those exact accounts. - [ ] Run the pinned labels bootstrap after the repository runner issue is complete. - [ ] Verify every core label from `.ceremony/LABELS.md` exists with the expected description/color. - [ ] Exercise issue queue reconciliation and PR state/blocker reconciliation. - [ ] Document how Forgejo dispatches the bootstrap/sweep and any platform-specific difference from GitHub. ## Acceptance criteria - [ ] `panel=` resolves to the accounts that actually review Forgejo PRs; author exclusion produces the correct required set. - [ ] `triage-actors=` resolves to the account(s) authorized to normalize issues. - [ ] Core labels include `needs-triage`, `ready`, `claimed`, `blocked`, `epic`, `needs-ruling`, `attention`, `offsite`, every `state:*`, and every `blocker:*` named by the pinned doctrine. - [ ] A new direct issue receives/retains a valid issue-flow state and malformed queue combinations are reported or repaired per Ceremony. - [ ] A draft PR, an active review round, an addressing round, and a fully approved current head reconcile to the documented state labels. - [ ] Re-running bootstrap is idempotent and preserves hand-set intent/scope labels. ## Test plan - Run the pinned labels bootstrap and work-queue sweep twice. - Compare the Forgejo labels API to `.ceremony/LABELS.md` and `.github/labels.conf`. - Drive representative issue/PR events and inspect label timelines plus workflow logs. - Confirm !114's configured panel would be Claude/Kimi/Codex minus its Grok author at its current head. ## Dependencies Blocked by #115.
codex-bot-andresmgsl added the
blocked
bug
scope:labels
 labels 2026-07-29 15:09:21 +00:00
codex-bot-andresmgsl commented 2026-07-30 17:51:01 +00:00
Author
Member
Copy link

Pre-run configuration is implemented in draft !128:

#128

The PR updates panel=, triage-actors=, the matching CONTRIBUTING.md roster, and exact regression tests. It uses Refs #116, not Closes #116, because the runner-backed acceptance criteria remain outstanding.

Parked: !128 is blocked on #115. After the runner is active, #116 still owns the taxonomy bootstrap and live issue/PR reconciliation. @andres is tagged on the PR to confirm the sole triage actor before merge.

Pre-run configuration is implemented in draft !128: https://forgejo.heavyduty.builders/heavy-duty/rig/pulls/128 The PR updates `panel=`, `triage-actors=`, the matching `CONTRIBUTING.md` roster, and exact regression tests. It uses `Refs #116`, not `Closes #116`, because the runner-backed acceptance criteria remain outstanding. Parked: !128 is blocked on #115. After the runner is active, #116 still owns the taxonomy bootstrap and live issue/PR reconciliation. @andres is tagged on the PR to confirm the sole triage actor before merge.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
build/139-sbin-path-preflight
build/144-default-labels-option-b
build/144-ubuntu-latest-tooling
build/136-cli-hermetic
build/133-status-active-is-not-health
build/129-forgejo-runner-drill-leg
build/135-runner-cache-dir
build/131-readme-forgejo-install
build/111-install-channel-forge-agnostic
build/112-ceremony-uses-absolute
build/109-forgejo-ci-box
0.3.1
0.3.0
0.2.0
0.1.0
Labels
Clear labels   
attention

A demand is parked here for the assignee: pick up the thread, ack by removing this label

  
blocked

Waiting on another PR or issue to land first

  
blocker:ci-red

A check is failing — the agent owes a fix (not a rebase)

  
blocker:conflict

Does not merge — the branch conflicts and the agent owes a rebase

  
blocker:drill-pending

Release ceremony is correct but has no drill record yet

  
blocker:unrequested

Somebody still owes a verdict and nobody was asked for one

  
bug

Something isn't working

  
claimed

A builder owns it: assignee set, draft PR expected shortly

  
documentation

Improvements or additions to documentation

  
enhancement

New feature or request

  
epic

Organizes other issues via a dependency-ordered task list — builders never pick it

  
merge-next

Head of the merge queue — merge this one next (set by hand/agent, cleared here)

  
needs-ruling

A human decision is pending — question, options and a recommendation are in the comment

  
needs-triage

Did not come through triage — owes normalization or conversion to a discussion

  
offsite

Issue deliverable is a PR in another repository — claim clock paused

  
post-merge

Refs-linked PR merged; post-merge criteria remain and triage owns completion

  
ready

Triaged, spec complete, unblocked — a builder can start now and succeed

  
release

Release flow and version/packaging work

  
scope:bootstrap

bootstrap — hardening a pristine server into a node

  
scope:coolify

coolify-* — Coolify and backup install

  
scope:db

db.sh — dump/restore

  
scope:docs

README, CONTRIBUTING, docs/ — the prose contract

  
scope:drill

drill/ and drills/ — the harness, its legs and its records

  
scope:installer

install.sh — how rig lands on a machine

  
scope:labels

the labels workflow, the reconciler, labels.conf and labeler.yml

  
scope:platform

rig platform — machine facts and identity, converged or not

  
scope:runner

runner-* — GitHub runner lifecycle

  
scope:users

users-* — class model, apply/status, close-root

  
stale

No activity for 48h — needs a poke (sweep-managed)

  
state:addressing

All bots reviewed — coding agent owes the single reply + fixes

  
state:bots-reviewing

Waiting on the bot reviewers to finish the round

  
state:building

PR is a draft — the coding agent is still building

  
state:needs-human

No blockers, all bots approve — waiting on the human reviewer

No labels
attention
blocked
blocker:ci-red
blocker:conflict
blocker:drill-pending
blocker:unrequested
bug
claimed
documentation
enhancement
epic
merge-next
needs-ruling
needs-triage
offsite
post-merge
ready
release
scope:bootstrap
scope:coolify
scope:db
scope:docs
scope:drill
scope:installer
scope:labels
scope:platform
scope:runner
scope:users
stale
state:addressing
state:bots-reviewing
state:building
state:needs-human
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: heavy-duty/rig#116
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?