conductor/rune
1
2 Fork 1
Code Issues 38 Pull Requests 28 Actions 26 Packages Projects Releases 564 Wiki Activity

fix(release): auto-bump push — HEAD:master + token auth (detached HEAD) #171

Closed
conductor wants to merge 1 commits from fix/auto-bump-push into master
pull from: fix/auto-bump-push
merge into: conductor:master
Conversation 0 Commits 1 Files Changed 1
+20 -5
conductor commented 2026-09-06 00:36:33 +01:00
Owner
Copy link
Copy source

Plain summary

The auto-bump workflow (merged in #170) failed on its first real run: git push origin master → "src refspec master does not match any" because Actions checks out a detached HEAD (the merge commit sha), not a branch. Fix: push HEAD:master and inject the GITEA_TOKEN into the remote URL for authentication.

How to test (layman's terms)

  1. Merge any small PR without a version bump.
  2. The auto-version workflow should now succeed: "Auto-bump: X.Y.Z → X.Y.Z+1" in the log, a new release appears, and master gets the auto-bump commit.
  3. If it still fails, check the Actions log for the exact error.

Technical details

  • git push origin master → git push origin HEAD:master (works from detached HEAD)
  • git remote set-url origin "https://conductor:${{ secrets.GITEA_TOKEN }}@..." before the push (self-hosted Gitea needs the token for push auth)
  • YAML validated.
## Plain summary The auto-bump workflow (merged in #170) failed on its first real run: `git push origin master` → "src refspec master does not match any" because Actions checks out a detached HEAD (the merge commit sha), not a branch. Fix: push `HEAD:master` and inject the GITEA_TOKEN into the remote URL for authentication. ## How to test (layman's terms) 1. Merge any small PR without a version bump. 2. The auto-version workflow should now succeed: "Auto-bump: X.Y.Z → X.Y.Z+1" in the log, a new release appears, and master gets the auto-bump commit. 3. If it still fails, check the Actions log for the exact error. ## Technical details - `git push origin master` → `git push origin HEAD:master` (works from detached HEAD) - `git remote set-url origin "https://conductor:${{ secrets.GITEA_TOKEN }}@..."` before the push (self-hosted Gitea needs the token for push auth) - YAML validated.
conductor added 1 commit 2026-09-06 00:36:34 +01:00
fix(release): auto-bump push uses HEAD:master + token auth (detached HEAD in Actions)
CI Pipeline / lint (push) Successful in 1m54s
Details
CI Pipeline / unit-tests (push) Successful in 2m16s
Details
CI Pipeline / canary (push) Failing after 1m31s
Details
CI Pipeline / best-practices (push) Successful in 5s
Details
CI Pipeline / documentation (push) Successful in 4s
Details
CI Pipeline / type-check (push) Successful in 2m11s
Details
CI Pipeline / gitea-offline (push) Successful in 39s
Details
Auto-label / priority-gate (pull_request) Skipped
Details
CI Pipeline / required-checks (push) Skipped
Details
Auto-label / auto-label (pull_request) Successful in 2s
Details
CI Pipeline / lint (pull_request) Successful in 1m56s
Details
CI Pipeline / unit-tests (pull_request) Successful in 2m8s
Details
CI Pipeline / canary (pull_request) Failing after 1m30s
Details
CI Pipeline / best-practices (pull_request) Successful in 5s
Details
CI Pipeline / documentation (pull_request) Successful in 4s
Details
CI Pipeline / type-check (pull_request) Successful in 2m3s
Details
CI Pipeline / gitea-offline (pull_request) Successful in 39s
Details
CI Pipeline / required-checks (pull_request) Skipped
Details
Auto-version and Release / release (pull_request) Failing after 5s
Details
f79407fa65 
The Actions checkout is on a detached HEAD (merge commit sha), so
'git push origin master' fails with 'src refspec master does not match
any'. Fix: push HEAD:master. Also inject the GITEA_TOKEN into the remote
URL so the push authenticates.
conductor closed this pull request 2026-09-06 00:42:26 +01:00
conductor deleted branch fix/auto-bump-push 2026-09-06 00:42:27 +01:00
gitea-actions Bot added the bugcustodian labels 2026-09-06 00:45:11 +01:00

Pull request closed

This pull request cannot be reopened because the branch was deleted.
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
Clear labels
P0 — critical
Spine/core correctness or blocks other work — do first
 P1 — high
Material user value or real defect (money, bugs, next-stage dep)
 P2 — medium
Quality/consolidation improvement
 P3 — low
Measurement / benchmark / deferred policy
 blocked
Dependencies open
 bug
Confirmed defect or regression
 custodian
epic
Rune v1 course-correction issue graph
 feature
New capability or improvement
 governance
growth
identity
in-progress
Currently being worked on by Rune
 incomplete
Incomplete work — draft PR with ledger, awaiting resume
 infrastructure
life
memory
memory-atlas
Memory Research Atlas child domain
 needs-testing
Needs manual testing with dumbed-down steps before close
 perception
ready
Order satisfied - Rune may start
 release-drift
research
Research jobs — spikes, watchlists, evidence work
 rune
rune
 scaffolding
scaffolding
 spine,correction
spine,correction
 spine,deferred
spine,deferred
 spine,resolved
spine,resolved
 strangler,burn,endgame,deferred
strangler,burn,endgame,deferred
 strangler,burn,endgame,inventory,epic
strangler,burn,endgame,inventory,epic
 tui
tui
 tui,epic
tui,epic
 tui,openspec
tui,openspec
 v1-course-correction
Rune v1 course-correction issue graph
No labels bug custodian
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
conductor
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: conductor/rune#171