feat(engine): push run branch to remote on loop_restart#6
Merged
danshapiro merged 1 commit intoFeb 10, 2026
Merged
Conversation
…outcome Add best-effort git push support so completed work is pushed to a configured remote after each loop_restart (feature completion) and on terminal outcome. This prevents data loss during long-running autonomous pipeline executions. New config field: git.push_remote (optional, string) New progress events: git_push_start, git_push_ok, git_push_failed Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Owner
|
🎉 This is fantastic work! The best-effort push design is exactly right — protecting long-running autonomous runs from data loss without ever risking an abort on push failure is a really elegant approach. The defensive nil checks, the clean progress event lifecycle ( I added a small hardening commit on top:
All tests passing. Merged — great contribution! 🚀 — Codex |
danshapiro
pushed a commit
that referenced
this pull request
Feb 14, 2026
- Fix #1: goreleaser check now uses command -v guard, not error masking - Fix #2: remove hardcoded occurrence counts from commit message - Fix #3: add Safety section update to release skill edits - Fix #4: add RELEASE_NOTES.md mechanism for hand-crafted release notes - Fix #5: add version_test.go for --version output coverage - Fix #6: use fully qualified brew install danshapiro/kilroy/kilroy Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This was referenced Apr 24, 2026
mattleaverton
added a commit
that referenced
this pull request
Apr 27, 2026
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.
Summary
git.push_remoteconfig field to run configloop_restart(before starting fresh iteration) and on terminal outcome persistencegit_push_start,git_push_ok,git_push_failed) but never abort the rungitutil.PushBranchhelper andEngine.gitPushIfConfiguredmethodMotivation
During long-running autonomous pipeline executions (e.g., feature factories that loop for hours), all committed work lives only on the local run branch until the user manually pushes. If the machine dies, hours of work are lost. This change ensures completed work is pushed to a remote after each successful loop iteration.
Usage
Test plan
TestGitPushIfConfigured_NoPushRemote- no-op when push_remote is emptyTestGitPushIfConfigured_NilRunConfig- no-op when config is nilTestGitPushIfConfigured_NilEngine- no-op on nil receiverTestGitPushIfConfigured_PushesToRemote- verifies branch appears on bare remoteTestLoopRestart_PushesOnRestart- full integration: loop_restart triggers push to bare remotego vetcleango build ./...clean🤖 Generated with Claude Code