GitButler

Feedback and tips for people who have issues: So initially I had issues getting it to run in my repo and it was because changes from develop to main branch were too big (60 commits). It was just loading forever. I had to delete the repo and then set it up as develop the target (trunk) branch instead of main. Then I was very careful not to do too many operations at the same time and I was able to checkout into a feature branch which branched from develop. No issues after that (except all changes from develop have the wrong blame history.

Hey Nicolás, I am sorry that you experienced issues setting it up. If you ping me on our Discord I can help you straight away (there is also a feedback button in the app in the bottom left if that's better for you). Thanks, Kiril

Very buggy, can't even connect my repo

GitButler started as a pretty simple observation that the way in which we use Git today hasn't changed much from how version control systems have worked for decades now. There is so much we can still do to improve how we work with, share, merge and collaborate on our code with more modern development workflows. The GitButler client is a Git client that doesn't just try to map buttons onto all the Git commands, but tries to think about what you're really trying to do and approach the problem new. Our first big focus is a totally new way to work on branches - simultaneously. You don't have to choose to be working on branch A or branch B and stashing and switching back and forth between them. You can have _both_ applied at the same time, adding to them, committing on them, pushing them to GitHub, without them getting entangled. The project is public on GitHub, so go check out the code, build it yourself, open any issues for bugs or just cool things you would love to see us solve for you. Thanks! Scott