Skip to content

SK-3002 Fix release workflow: v3 branch/path ambiguity#369

Merged
Devesh-Skyflow merged 1 commit into
v3from
devesh/SK3002-fix-workflow
Jul 22, 2026
Merged

SK-3002 Fix release workflow: v3 branch/path ambiguity#369
Devesh-Skyflow merged 1 commit into
v3from
devesh/SK3002-fix-workflow

Conversation

@Devesh-Skyflow

Copy link
Copy Markdown
Collaborator

Problem

The release workflow (beta/public) failed in the Commit changes step:

fatal: 'v3' could be both a local file and a tracking branch.
Please use -- (and optionally --no-guess) to disambiguate
Error: Process completed with exit code 128.

Root cause: the step ran git checkout ${{ env.branch_name }} (i.e. git checkout v3). Because the repo now contains a v3/ directory (see the git add v3/pom.xml line right below), the argument v3 is ambiguous between the branch v3 and the path v3/, so git bails out.

Fix

Use git switch instead of git checkout in .github/workflows/shared-build-and-deploy.yml. git switch only ever operates on branches, so the branch/path collision cannot occur.

- git checkout ${{ env.branch_name }}
+ git switch ${{ env.branch_name }}

The git push origin ${{ env.branch_name }} lines are unaffected — push refspecs are not ambiguous with paths.

🤖 Generated with Claude Code

…ambiguity

The Commit changes step ran 'git checkout v3'. Since the repo now contains a
v3/ directory, git could not disambiguate the 'v3' branch from the 'v3' path
and failed with: fatal: 'v3' could be both a local file and a tracking branch.

Use 'git switch' instead, which only operates on branches.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@Devesh-Skyflow
Devesh-Skyflow merged commit b009590 into v3 Jul 22, 2026
2 checks passed
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