Skip to content

fix: use full clone in v1 branch update workflow - #57

Closed
tend-agent wants to merge 1 commit into
mainfrom
hourly/review-23561280795
Closed

tend-agent wants to merge 1 commit into
mainfrom
hourly/review-23561280795

Conversation

@tend-agent

Copy link
Copy Markdown
Collaborator

Summary

  • Adds fetch-depth: 0 to the checkout step in the v1 branch update workflow so git has full history to prove the fast-forward push

Root cause

The "Update action branch" workflow uses a shallow clone (default fetch-depth: 1), which only has the tip commit. When pushing HEAD:refs/heads/v1, git cannot prove to the remote that the push is a fast-forward without the common ancestor in local history. The remote rejects with:

! [rejected]        HEAD -> v1 (fetch first)
error: failed to push some refs to 'https://github.com/max-sixty/tend'
hint: Updates were rejected because the remote contains work that you do not
hint: have locally.

This broke the v1 auto-update when PR #55 merged, keeping v1 stuck at fbf397e while main advanced to 9466b6a. The compat fix (PR #54) — which unblocks all adopter review runs — cannot reach adopters until v1 is updated.

Evidence

  • Failed run: 23561357476 — git push origin HEAD:refs/heads/v1 rejected
  • v1 status: 4 commits behind main, 0 ahead (confirmed via GitHub compare API)
  • Impact: All tend-review runs on adopter repos (e.g. max-sixty/worktrunk) continue failing with Unknown skill: tend:tend-review because v1 still points to pre-compat code

Gate assessment

  • Evidence level: Critical — clearly wrong outcome (v1 update mechanism is completely broken, preventing fixes from reaching adopters)
  • Occurrences: 1 (the first and only run of this workflow since PR fix: use v1 branch instead of floating tag #55 merged)
  • Change type: Targeted fix (add one parameter to checkout step)
  • Passes both gates: Yes

Test plan

  • Merge this PR to trigger the workflow on the push-to-main event
  • Verify the "Update action branch" workflow succeeds
  • Confirm v1 branch SHA matches main after workflow completes

🤖 Generated with Claude Code

The shallow clone (default fetch-depth: 1) causes git push to fail with
"remote contains work that you do not have locally" because the local
repo can't prove the fast-forward to the remote without full history.

This broke the v1 auto-update after PR #55 merged, keeping v1 stuck at
fbf397e while main advanced. As a result, the compat fix in PR #54
cannot reach adopters even after merge.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@tend-agent tend-agent added the claude-behavior Behavioral issues found by review-reviewers label Mar 25, 2026
@max-sixty max-sixty closed this Mar 25, 2026
@max-sixty
max-sixty deleted the hourly/review-23561280795 branch March 25, 2026 23:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

claude-behavior Behavioral issues found by review-reviewers

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants