add_worktree fails with non-bare repo
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1.7k
- Forks
- 408
- Avg merge
- 2d 57m
- Merged PRs (30d)
- 7
Description
I'm trying to add a worktree with
_pygit2.add_worktree(name, path, _pygit2.lookup_reference(ref))
ref is fetched using _pygit2.raw_listall_references(). This works for bare git repo.
In case of non-bare git repo, it fails with,
_pygit2.GitError: reference is not a branch
Contributor guide
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 with the _pygit2.add_worktree, _pygit2.lookup_reference, and _pygit2.raw_listall_references entry points. Reproduce the reported call with both bare and non-bare repositories and inspect how the reference is handled. Done means adding a worktree from the fetched reference works for a non-bare repository without the "reference is not a branch" error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, python
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100