sean/seanfarm
Watch
1
0
Fork
You've already forked seanfarm
 0
Code Issues Pull requests 1 Projects Releases 423 Packages Wiki Activity

docs: record that binjovictl is the release train and does the merge #457

Merged
binjovi-bot merged 1 commit from docs/release-train-binjovictl into trunk 2026-09-08 12:08:01 +00:00
Conversation 0 Commits 1 Files changed 1 +24 -1
sean commented 2026-09-08 12:07:42 +00:00
Owner
Copy link

Records the last step of the workflow, which was previously left to be guessed.

An agent that does not know binjovictl is the release train reaches for the
Forgejo merge API, gets refused, and then stops and asks for a permission it
never needed. That happened twice in one session. The First principles bullet
said "pull request" and stopped there.

Adds:

  • binjovictl release PROJECT --all-ready --wait merges the branch and
    moves trunk. Nothing merges a pull request by hand.
  • Wait for binjovictl status to report build succeeded on the commit before
    releasing it.
  • A deploy that fails part way through a reconcile wave is common and usually
    succeeds on binjovictl retry-deploy DEPLOYMENT_ID.
  • The binary is at ~/bin/binjovictl and is not always on PATH — which is why
    which binjovictl finds nothing and it looks absent.

CLAUDE.md is a symlink to AGENTS.md, so the change lands in AGENTS.md.

tests/check.sh passes.

https://claude.ai/code/session_01KZoQin34jeyt6nDGqvJA76

Records the last step of the workflow, which was previously left to be guessed. An agent that does not know `binjovictl` is the release train reaches for the Forgejo merge API, gets refused, and then stops and asks for a permission it never needed. That happened twice in one session. The `First principles` bullet said "pull request" and stopped there. Adds: * `binjovictl release PROJECT --all-ready --wait` merges the branch **and** moves trunk. Nothing merges a pull request by hand. * Wait for `binjovictl status` to report `build succeeded` on the commit before releasing it. * A deploy that fails part way through a reconcile wave is common and usually succeeds on `binjovictl retry-deploy DEPLOYMENT_ID`. * The binary is at `~/bin/binjovictl` and is not always on `PATH` — which is why `which binjovictl` finds nothing and it looks absent. `CLAUDE.md` is a symlink to `AGENTS.md`, so the change lands in `AGENTS.md`. `tests/check.sh` passes. https://claude.ai/code/session_01KZoQin34jeyt6nDGqvJA76
docs: record that binjovictl is the release train and does the merge
All checks were successful
binjovi/ci Binjovi completed the frozen plan
Details
0e7c04f1ee
 
An agent that does not know this reaches for the Forgejo merge API, gets
refused, and then stops and asks for a permission it never needed. That
happened twice in one session. The workflow bullet said "pull request" and
stopped there, so the last step was left to be guessed.

Write it down instead:

  * binjovictl release PROJECT --all-ready --wait merges the branch AND
    moves trunk. Nothing merges a pull request by hand.
  * wait for `binjovictl status` to report `build succeeded` on the commit
    before releasing it.
  * a deploy that fails part way through a reconcile wave is common and
    usually succeeds on `binjovictl retry-deploy`.
  * the binary is at ~/bin/binjovictl and is not always on PATH, which is
    why `which binjovictl` finds nothing and looks like it is absent.

CLAUDE.md is a symlink to AGENTS.md, so the change lands in AGENTS.md.

tests/check.sh passes.

Claude-Session: https://claude.ai/code/session_01KZoQin34jeyt6nDGqvJA76
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No labels
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
sean/seanfarm!457
No description provided.