GitBrain lets you simplify your Git workflow and maximize you coding productivity. Using AI, it intelligently understands your code changes and provides suggestions for Git operations.
Hey Product Hunt Community! Hey developers! 👋
I’m excited to introduce GitBrain, an AI-powered Git Client for Mac to all of you.
🚀 What's GitBrain all about?
As developers, we spend a lot of time working with git: creating commits, dealing with pull requests, resolving conflicts, and more. But let's face it, these git tasks are tiring and time-consuming. GitBrain is here to help you save time with git, so you can focus more on coding.
👉 What can GitBrain do for you?
The most frequently performed and tiring task in git is committing changes to repositories. GitBrain simplifies your git commit workflow by
- Providing an AI-generated summary of your code changes so that you can review it before committing
- Automatically splitting your code changes into multiple commits with AI-generated messages → Many times, we forget to commit at the right moment, resulting in a large batch of changes to commit all at once. It becomes a hassle to figure out what we've been working on and how to split it using Git clients. With GitBrain, all of that is taken care of for you, saving you time and making the process much more convenient.
- GitBrain can automatically detect your Git repositories from your IDEs, eliminating the need to manually import them. This way, the projects you're currently working on will be conveniently displayed at the top of the list, allowing for easy access and management without any extra effort.
- Accessible with a simple keyboard shortcut, allowing you to commit with just few key strokes.
⭐ Where are we going next?
1. We're working on creating more lightweight UIs for git interactions. Imagine being able to commit right from your menu bar!
2. We plan to expand GitBrain's features to cover even more git tasks. Our goal is to make GitBrain write pull requests and suggest helpful git operations, so you can focus solely on your code.
To thank our early supporters, we are offering a limited number of free lifetime licenses for GitBrain's beta users. Join us quickly! And even after that, you can use the code M5NJY3NA for a 50% discount.
We're a small team of developers who want to build useful tools that make developers more productive. We highly value your feedback and suggestions. Come join us, and let's create an AI-powered git client together!
I went ahead and decided to support this product. The direction is an intriguing concept so far. I haven't been able to put it through "the wringer" yet, but the results so far are promising. It doesn't look like it is a full replacement for a Git GUI, but I can see the benefit for just committing code. The ability to edit commit messages and double-check what I'm committing is pretty important for me. I look forward to seeing how this product evolves. :)
Thank you, @adam_presley, for your support and valuable feedback!
We've received several requests from users to have the ability to edit commit messages before committing. In the next version, we will be addressing this feature. I have a few questions related to your feedback:
1. When it comes to editing commit messages, which option do you prefer?
a) Editing the prefix part (feat, fix, etc.) and description separately, with the ability to edit the prefix tag through a dropdown UI.
b) Editing the commit message as a whole.
2. Could you please provide more details on what you mean by "double-checking"? Are you referring to reviewing the code changes you've made, checking how the AI has split your code changes, or checking after the commit process is completed?
Thanks again for your support!!
@kiwhan
1. Option "a" is nice, but "b" is fine too honestly. I can always imagine scenarios where I may need to provide more "color" as to the "why" in a commit
2. Oftentimes I will review the files that are changed. Many times this is just for peace of mind. Other times, I may not be ready to commit a file yet, or a file should NOT be committed (and added to the gitignore). In other situations, I may want to only commit a partial chunk of a file.
@adam_presley Thank you for your response! We have been receiving similar feedback from other users, and we are committed to figuring out what would be best for our users moving forward.
@kiwhan Thank you for considering feedback. And I certainly appreciate it if this tool is designed to be "laser focused" on just doing commits well. I would still find it a useful tool in my "tool belt" just the same.
@adam_presley GitBrain is currently focused on doing commits well, but it will evolve and offer additional features through future updates. I'm glad to hear that you find GitBrain helpful!
GitBrain
GitBrain
GitBrain
GitBrain
Sugar Free: Food Scanner
GitBrain