Skip to content

fix(cli): task-setup uses --path-format=absolute for git-common-dir #900

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
buremba merged 1 commit into from
May 19, 2026
Merged

fix(cli): task-setup uses --path-format=absolute for git-common-dir #900

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 8 additions & 1 deletion scripts/task-setup.sh
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -83,7 +83,14 @@ script_dir="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
# main repo's .git path) regardless of which worktree the call is made from.
# Its parent is the main checkout — exactly what we want for both the
# `git worktree add` target and the `.env` source.
repo="$(cd "$(dirname "$(git -C "$script_dir" rev-parse --git-common-dir)")" && pwd)"
#
# `--path-format=absolute` is load-bearing. Without it, `--git-common-dir`
# returns a path relative to git's cwd ("../.git"), and `dirname` of that
# resolves against whatever directory the caller happens to be in — landing
# the worktree at the wrong path (e.g. /Users/burakemre/Code instead of
# /Users/burakemre/Code/lobu when run from the main checkout). The absolute
# form makes the resolution invariant.
repo="$(dirname "$(git -C "$script_dir" rev-parse --path-format=absolute --git-common-dir)")"
worktree_dir="$repo/.claude/worktrees/$name"
branch="feat/$name"

Expand Down
Loading