3 ms·
I 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 k
by crazygringo 15y ago
I 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!)