4 thoughts on “Git integration doesn’t work if .git/ not in top level

  1. I would love to have this implemented. I prefer to have my git repositories neatly nested inside a parent folder. It doesn’t make sense that I should have to open the individual git project outside of that parent folder and clutter up my sidebar more than need be.

    Don’t get me wrong, The git integration in Atom is awesome, but I think I’ll be sticking with using git on command line until I am able to at least toggle something in the settings that allows me to track changes to git repositories stored in a sub-project folder.

  2. For what it’s worth, I think there’s a pretty easy workaround for this. I’d been trying to get this working by opening the parent directory that had all my projects in it, but that does not work because there is no .git folder in that parent directory. It does work, however, if I open one of the project folders that is contained in the parent directory, then individually open each other project folder in that directory with the “Add Project Folder…” function in the editor. For example, let’s say I have this folder structure:

    projects
    ├── my-first-project
    │   └── .git
    ├── my-second-project
    │   └── .git
    ├── my-third-project
    │   └── .git
    

    What I was doing before that did not work was opening the projects folder. What I did that does work was individually open each of my-first-project, my-second-project, and my-third-project. It is a bit of a pain to open each project folder like that, but Atom will remember your recent projects so I think it’s pretty manageable once you’ve opened them. And then this actually works, so there’s that.

    http://blog.atom.io/2015/04/15/multi-folder-projects.html

  3. You can include me as a developer that works with projects with >50 repos on a daily basis. This issue is one of my biggest holdouts from switching from Sublime honestly.

    Besides the group of us who have specific large repo cases, here’s a more wide spread audience example – think ansible roles. One repo per ansible role, and that list of repos grows very fast.