Problems with certain git repos in GitKraken and Atom, causing Atom to be unusable

git magento atom-editor gitkraken
Joren Rapini picture Joren Rapini · May 13, 2016 · Viewed 8k times · Source

We have recently tried switching from Sublime to Atom, and started using GitKraken also (we've mostly just been working with git in command line)

We have some projects with git in it that cause serious issues. One main was that we work in almost daily is a Magento 1.9 site (although, we have other Magento 1.9 sites on git repos that have no problem with Atom). What happens is we open the project in Atom and we cannot open any files. It seems to hang on initializing git info (folders stay uncolored).

Sometimes when we open up the project in Atom it works, most of the time it doesnt. We HAVE noticed a 1:1 correlation with GitKraken when this occurs - when we try to open the repo in gitkraken we get an error that it could not find any repo - even though it actually loads the repo just fine, albeit after a long delay. Other time this does not occur, and that's when it opens fine in Atom. We could leave it sitting there for a couple of hours untouched and come back to it and all of a sudden we cannot open any files. This happens to all users in the office.

The problem with atom is definitely related to git. If we remove the repo and open the project then it works with no issues.

I thought, maybe repo size or history had something to do with it, so we tried initializing a fresh repo, added the files and made our first commit, and still the same problem. Our git ignore file is almost identical to the other magento sites that have no problems with Atom or Gitkraken.

Honestly it's such a weird problem I don't even know who to submit the bug report to, and we haven't found anything in our searching.

**** One thing that we've discovered of note, every time we have this issue, if we run Git GUI within that git repo folder (simply just open git gui) then all of the problems with Atom and GitKraken disappear for a time. Eventually the problems just come back though.

Answer

rmunn picture rmunn · Dec 15, 2016

This is a very late answer to a six-month old issue, and this might not be the actual problem. But I just found a repo that GitKraken couldn't handle, and narrowed down the problem. Turned out that in that repo's .git/config file, there were two sections with the following configuration:

[gitflow "branch"]
    master = master
    develop = develop
[gitflow "prefix"]
    feature = feature/
    release = release/
    hotfix = hotfix/
    support = support/

With those two sections in the repo's .git/config section, GitKraken wouldn't open the repo: it would just sit there with its "busy" spinner spinning, and spinning, and going nowhere. But if I removed those two gitflow sections from .git/config, GitKraken easily opened the repo, and the "busy" spinner was visible for just 2-3 seconds.

So if your repo uses git-flow, try removing those two config sections from a local copy of the repo and see if that allows Git Kraken to open it.

Related questions

Best practices for using Git with Magento?

I'm working at figuring out how to best work within my own repo for custom code while integrating with a vendor's library (in this case Magento). In my case, I will not need to push up patches to the vendor (…

Read More
How do I undo the most recent local commits in Git?

I accidentally committed the wrong files to Git, but didn't push the commit to the server yet. How can I undo those commits from the local repository?

Read More
How do I delete a Git branch locally and remotely?

I want to delete a branch both locally and remotely. Failed Attempts to Delete a Remote Branch $ git branch -d remotes/origin/bugfix error: branch 'remotes/origin/bugfix' not found. $ git branch -d origin/bugfix error: branch 'origin/bugfix' not …

Read More