Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

ghcd for the agentic era

Open
  • Is something wrong?
#47 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
55/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
shell
Domain
cli

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.

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 ...

Dominant language
Shell
Stars
1
Forks
0
Avg merge
11m
Merged PRs (30d)
2

Getting set up

  • No Dockerfile or Docker Compose file
  • Has a pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from indexzero/dotfiles

All issues in indexzero/dotfiles

Similar issues

More Shell/Bash issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.