indexzero / indexzero/dotfiles
ghcd for the agentic era
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 1
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
I find myself regularly stuck in a "dead" worktree because I have a session or two running there. This systemic problem would be resolved ghcd user/repo did NOT clone / goto:
$GIT_ROOT/user/repo
but instead went to:
$GIT_ROOT/user/repo/$MAIN_BRANCH
In turn the worktree root then becomes:
$GIT_ROOT/user/repo
instead of:
$GIT_ROOT/user/repo-worktrees
All of that seems like one less quirk to worry about ...
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the ghcd command entry point in the repository and read how it chooses the clone and worktree paths. Reproduce the reported behavior with ghcd user/repo, then verify that the repository is placed at $GIT_ROOT/user/repo and its main branch worktree at $GIT_ROOT/user/repo-worktrees.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- shell
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100