Skip to content

Push source stack branches through the CAOS server - #265

Closed
nishu-builder wants to merge 2 commits into
codex/stack-drafts-20260919-01a0978afrom
codex/stack-submit-20260919-01a0978a
Closed

nishu-builder wants to merge 2 commits into
codex/stack-drafts-20260919-01a0978afrom
codex/stack-submit-20260919-01a0978a

Conversation

@nishu-builder

@nishu-builder nishu-builder commented Sep 19, 2026 •

Copy link
Copy Markdown
Contributor

Adds push_stack to publish the branches in a registered source stack directly from the CAOS server. It takes an HTTPS repository URL and uses each source gitlink's path as its branch name. No checkout or GitHub worker is needed.

All commits and remote-head leases are saved before the first push. Branches are pushed bottom to top through the same path as publish_source. Both tools save each push result before completing the call or moving to another branch, so recovery keeps the original inputs and skips completed pushes. A failure returns partial progress.

If a push command succeeds but returns unreadable output, the tool checks the remote branch to find out whether the push completed.

PR creation and GitHub stack membership are left for a separate change.

@nishu-builder
nishu-builder added this pull request to stack #261 September 19, 2026 01:44
@nishu-builder
nishu-builder force-pushed the codex/stack-submit-20260919-01a0978a branch from c6f932a to 56ad570 Compare September 19, 2026 02:38
@nishu-builder nishu-builder changed the title Submit and resubmit source gitlink stacks to GitHub Push source stack branches through the CAOS server Sep 19, 2026
Incorporate the simplifications from #266. Both publication tools retain remote outcomes through the same durable record path, and unreadable successful command results are reconciled against the remote branch.

Copy link
Copy Markdown
Contributor Author

Closing with the rest of stack #261. A stack is now published with create-squashed-stack and one publish_source per layer (#291). Opening a PR per layer and linking them is designed in #300.


Generated by Claude Code

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant