does not work with GITs 2.5 worktree feature #344
Comments
As GitPython is in maintenance mode, there will be no new features. However, I believe it's good idea to explicitly state we do not support certain things if this is the case. Therefore, when worktrees are encountered, we will throw an specific exception to indicate that. The current implementation is hacky to speed up development, and increases the risk of failing due to false-positive worktree directories. Related to #344
|
Thank for letting me know ! As GitPython is in maintenance mode, I won't be adding any new features. However, I added a check to throw an exception specific to worktrees, letting people know the feature is not supported that way. Thanks for your understanding |
|
You can watch the development stream on youtube.
|
|
@Byron Can this be reopened, with the advent of 2.x? |
|
Hi @fooishbar , the reason for closing this issue is still valid, despite the recent major release. The latter just means there have been breaking API changes, that could affect people negatively. |
|
@Byron That's a shame. Do you know of any other Python-based git libraries which are tracking new Git features, e.g. worktrees? |
|
@fooishbar I don't, but that means nothing. Most people might help themselves by using GitPython to call git in a more pythonic fashion, which is why this library is still used a lot. |
|
@Byron OK, thanks! |
|
Hi, I was wondering if there was any support for this issue yet? |
|
It would be great if support for additional worktrees is added. Now I'll have to abandon GitPython and find another solution. |
|
For future reference - I figured out how to use worktree. It's not wrapped but interacting with Repo.git manually works perfectly fine. Tutorial here; #719 |
Steps to reproduce (assumes GIT >= 2.5 and a repo with at least 2 branches)
git checkout <whatever>git worktree add /tmp/foo another_branch/tmp/fooimport git; git.Repo('.')in Pythongit.exc.InvalidGitRepositoryErrorThe text was updated successfully, but these errors were encountered: