search

subesokun / atom-tree-view-git-status

Shows the Git repository status in the Atom tree-view
MIT License
24 stars 2 forks source link

Add support for worktrees #19

Closed karrots closed 8 years ago

karrots commented 8 years ago

When a work tree is added to the project it doesn't show status.

subesokun commented 8 years ago

Hi @karrots, do you mean that in case of adding a new "Project Folder" while Atom is running then the Git status is not shown correctly? Or generally no Git status is shown in the tree view? Could you tell me which version of Atom you're using and which version of tree-view-git-status? A screenshot would be also great.

karrots commented 8 years ago

No status is shown in the tree view for the work tree folder only. The master branch shows status. It looks as though it's just a standard folder.

atom-tree-view-git-status 0.2.2 Atom version 1.4.0

https://goo.gl/photos/QHS6HVhZNpTD15Nx7

subesokun commented 8 years ago

Hi @karrots, sorry for the delay. Actually for me everything looks ok. For your first project folder the git status gets correctly displayed and your second project folder seems like to have no Git folder (.git is missing) hence Atom will not recognize it as a Git repository. Are you sure that this RaspberryPi-Gateway-imagebuilder folder is under version control?

karrots commented 8 years ago

Yes it is a Git worktree so there is no .git folder just a .git file reference to the main repository. All of the version control information is stored centrally in the main repo.

subesokun commented 8 years ago

@karrots Mhh I see. Then it seems that Atom itself, to be more precise the git-utils, has some issues at recognizing such Git worktree :( The tree-view-git-status package just reads out the SCM informations received from Atom so there's not so much I can do at the moment for you. Please feel free to create an issue on the git-utils repo, or open a discussion on atom.io and I'd be great if you could post here a link then.

subesokun commented 8 years ago

Closing this issue as it's Atom related and thanks for reporting the issue in the git-utils repo :+1: