Fast-forward autoloop/* branches when ahead=0 instead of merging#43
Merged
Fast-forward autoloop/* branches when ahead=0 instead of merging#43
Conversation
Agent-Logs-Url: https://github.com/githubnext/autoloop/sessions/d8693a27-49f0-457c-bc7e-39d13e16a9bc Co-authored-by: mrjf <180956+mrjf@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Update branch handling to fast-forward when ahead=0
Fast-forward autoloop/* branches when ahead=0 instead of merging
Apr 22, 2026
Contributor
|
@copilot fix tests |
Agent-Logs-Url: https://github.com/githubnext/autoloop/sessions/eb03ca6e-1e28-4ca4-aa3d-bd15025f0fee Co-authored-by: mrjf <180956+mrjf@users.noreply.github.com>
Contributor
Author
Fixed in a7c81f5. The CI failure was |
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.
The unconditional
git merge origin/mainin Step 3 (and in the companionsync-branchesworkflow) produced noisy "Merge main into branch" commits whenever a long-running branch had no unique commits. Those merge commits re-exposed every historical file as a patch touch, aggregating to >100 file changes on the next iteration's PR and tripping gh-aw's hard-codedE003limit.Changes
workflows/autoloop.md— Replaced the Step 3 prose (and its content-deltagit diffheuristic + baregit reset --hard) with an explicit four-case decision tree keyed ongit rev-list --countahead/behind:push --force-with-leaseworkflows/sync-branches.md(Node.js template) and.github/workflows/sync-branches.md(deployed Python copy) — Same four-case logic in the per-branch sync loop, so the companion workflow cannot re-introduce the noisy merge commits the per-iteration step now avoids..github/workflows/sync-branches.lock.yml— Regenerated viagh aw compile, with the two pre-existing manual fixups re-applied (permissions: contents: write; merge step ordered afterConfigure Git credentials).--force-with-lease(not--force) so a concurrent push to the branch is rejected rather than clobbered. The fast-forward is lossless becauseahead=0proves every commit on the branch is already reachable frommain.