26 ms·
I really want to use GitHub for mac, but in my experience using it in conjunction with the command line doesn't work well. Just the other day I launched it to l
by cemregr 15y ago
I really want to use GitHub for mac, but in my experience using it in conjunction with the command line doesn't work well. Just the other day I launched it to look at my diff before pushing, upon launch it complained about a non existent merge conflict, put me on master making me lose uncommitted changes, and resurrected some weird files out of nowhere into my working directory. I feel like every time I open it, it's a surprise.
- kenneth_reitz 15y agoThat's why I wrote Legit :) http://kennethreitz.com/legit-the-sexy-git-cli.html http://kennethreitz.com/legit-the-sexy-git-cli.html
- crazygringo 15y agoI had the same experience -- it's so simple and beautiful to use, BUT every time I encountered a merge conflict it somehow wouldn't accept my resolutions, and kept re-generating the same conflict. I'd tried it both in "sync" mode, and in normal push/pull mode, and both of them kept corrupting my repository somehow. After this happened three times, I switched to SourceTree, which I haven't had any problems with. I think the #1 priority for GitHub for mac is to get the Git functionality itself actually working flawlessly. (Plus the constant random "empty dict" bug messages, etc., that pop up at random times during the day, even when I've just left it in the background!)
- RandallBrown 15y agoYeah the app was TERRIBLE at handling merge conflicts and errors. I loved the app until that happened and it would get in a bizarre state and stop working for awhile. Hopefully this fixes it.