Skip to content

does not work with GITs 2.5 worktree feature #344

Description

@crepererum

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
  • go to /tmp/foo
  • execute: import git; git.Repo('.') in Python
  • results in git.exc.InvalidGitRepositoryError

Activity

  1. added this to the v1.0.2 - Fixes milestone on Aug 29, 2015
  2. Byron commented on Aug 29, 2015

    @Byron
    Member

    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

  3. Byron commented on Aug 29, 2015

    @Byron
    Member

    You can watch the development stream on youtube.

    GitPython #23 [issue 344 - explicitly state worktrees are unsupported]

    thumb

  4. fooishbar commented on Oct 24, 2016

    @fooishbar

    @Byron Can this be reopened, with the advent of 2.x?

  5. Byron commented on Oct 25, 2016

    @Byron
    Member

    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.

  6. fooishbar commented on Oct 25, 2016

    @fooishbar

    @Byron That's a shame. Do you know of any other Python-based git libraries which are tracking new Git features, e.g. worktrees?

  7. Byron commented on Oct 25, 2016

    @Byron
    Member

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

  8. fooishbar commented on Oct 25, 2016

    @fooishbar

    @Byron OK, thanks!

  9. KellyDeveloped commented on Jan 18, 2018

    @KellyDeveloped

    Hi, I was wondering if there was any support for this issue yet?

  10. hilkoc commented on Jan 29, 2018

    @hilkoc

    It would be great if support for additional worktrees is added. Now I'll have to abandon GitPython and find another solution.

  11. KellyDeveloped commented on Jan 30, 2018

    @KellyDeveloped

    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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions