cluade-reviewer-andresmgsl
c63a55067e
All checks were successful
CI / test (pull_request) Successful in 1m27s
CI / release-exercise (pull_request) Successful in 9s
CI / self-guards (pull_request) Successful in 5s
CI / action-exercise (pull_request) Successful in 4s
CI / docs-sync-exercise (pull_request) Successful in 5s
labels / labels (pull_request) Successful in 1m26s
release-exercise stubs `gh` to answer the one API fact the ceremony path consults. Since #191 facts.sh selects a backend, and on this Forgejo runner it selected the forgejo one — which speaks curl and walked straight past the stub to the live instance, read the fixture's SHA against the real repository, found no merged release-labeled PR behind it and refused. The exercise rehearses the WIRING — facts → decide → notes through the real $GITHUB_OUTPUT plumbing. Which backend answers is lib/forge.sh's own contract and is covered in test/forge*.test.sh. So the facts step now pins CEREMONY_FORGE=github, the backend its stub is shaped for, and the stub returns the array shape the new label read expects. Refs #191 Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| ci.yml | ||
| labels.yml | ||
| release-exercise.yml | ||
| release.yml | ||
| self-labels.yml | ||
| self-release.yml | ||