shoko/kugetsu
1
0
Fork 0
Code Issues 17 Pull Requests Actions Packages Projects Releases 3 Wiki Activity

Worktree created in home directory instead of ~/.kugetsu-worktrees in v0.2.9 #185

New Issue
Closed
opened 2026-04-06 06:20:27 +02:00 by shoko · 0 comments
shoko commented 2026-04-06 06:20:27 +02:00
Owner
Copy Link

Bug

In v0.2.9, cmd_start creates worktrees in the daemon's working directory (/home/shoko) instead of ``.

Root cause: kugetsu-session.sh line 249 calls create_worktree without passing the `` argument. In create_worktree() (kugetsu-worktree.sh line 68), parent_dir defaults to /home/shoko:

local parent_dir="${2:-$PWD}"

Since the daemon runs from /home/shoko, worktrees end up at /home/shoko/git.fbrns.co-shoko-kugetsu-158 instead of ~/.kugetsu-worktrees/git.fbrns.co-shoko-kugetsu-158.

Affected versions: v0.2.9

Reproduction

  1. kugetsu queue-daemon start
  2. kugetsu delegate "https://git.fbrns.co/shoko/kugetsu/issues/158"
  3. Worktree created at /home/shoko/git.fbrns.co-shoko-kugetsu-158 instead of ~/.kugetsu-worktrees/

Fix

kugetsu-session.sh line 249:

# WRONG
create_worktree "$issue_ref"

# CORRECT
create_worktree "$issue_ref" "$WORKTREES_DIR"
## Bug In v0.2.9, `cmd_start` creates worktrees in the daemon's working directory (`/home/shoko`) instead of ``. **Root cause:** `kugetsu-session.sh` line 249 calls `create_worktree ` without passing the `` argument. In `create_worktree()` (kugetsu-worktree.sh line 68), `parent_dir` defaults to `/home/shoko`: ```bash local parent_dir="${2:-$PWD}" ``` Since the daemon runs from `/home/shoko`, worktrees end up at `/home/shoko/git.fbrns.co-shoko-kugetsu-158` instead of `~/.kugetsu-worktrees/git.fbrns.co-shoko-kugetsu-158`. **Affected versions:** v0.2.9 ## Reproduction 1. `kugetsu queue-daemon start` 2. `kugetsu delegate "https://git.fbrns.co/shoko/kugetsu/issues/158"` 3. Worktree created at `/home/shoko/git.fbrns.co-shoko-kugetsu-158` instead of `~/.kugetsu-worktrees/` ## Fix `kugetsu-session.sh` line 249: ```bash # WRONG create_worktree "$issue_ref" # CORRECT create_worktree "$issue_ref" "$WORKTREES_DIR" ```
shoko added the bug label 2026-04-06 06:20:27 +02:00
shoko closed this issue 2026-04-06 07:33:04 +02:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
0.2.x-only
Available only in 0.2.x, not backportable
 0.3.x-only
Available only in 0.3.x, not backportable
 backport
Backport compatible - can merge to 0.1.x
 blocked
Issue needs clarification/discussion before it can be worked on
 bug
Bug report
 critical
Critical - blocking parallel work
 feature
New feature
 foundation
Foundation work for 0.2.x
 high
High priority - workflow improvements
 meta
Meta issue tracking multiple issues
 need-review
PR needs review before merge
 parallelization
Issues related to parallelization
 ready
Issue is clear and ready to be implemented/delegated
 ready-to-merge
PR approved and ready to merge
 task-delegation
Issues related to task-delegation
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
shoko
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: shoko/kugetsu#185
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?