ci(queen): take the bees' work out of the container from the cloud, not a laptop - #4602
Merged
Merged
Conversation
…ot a laptop Closes #4601 Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Contributor
|
📓 NotebookLM Notebook linked to this PR
This notebook contains session context, decisions, and artifacts for this work. |
Contributor
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #4601
The container exports (it holds no push credential by design); nothing in the cloud pushed what it exported, so the chain ran only while somebody's laptop did. Measured this morning: last bee branch on GitHub 10:33 yesterday, 59 accepted issues whose work never left the container, swarm at 0 of 20 lanes.
export_push.pyreads the export list, fetches each branch as a bundle and pushes it; the workflow runs every 20 minutes and on demand. It never forces, and it names the one secret it needs (QUEEN_EXPORT_TOKEN= the agent server'sTRIOS_API_TOKEN) instead of skipping quietly.queen-publish.ymlalready runs on a push toqueen-*, so the pull request follows by itself.Self-test: 4 fixtures (oldest first, nothing for a branch level with the base, only
queen-<issue>names, the limit honoured).🤖 Generated with Claude Code