Kiril Videlov

Working very hard right now to squash all of them bugs! Sorry for the inconvenience

Managing Multiple Claude Code Sessions Without Worktrees With Claude Code's new lifecycle hooks, GitButler can now automatically sort simultaneous AI coding sessions into separate branches. Write three features at the same time, get three independent branch...

If you're using Claude Code, the latest GB release has a very cool hooks integration where it puts the output of each session you run into a new parallel Git branch.
Check it out 👇
blog.gitbutler.com/parallel-cla...

It maintains real git references with an integration octopus merge on top that is checked out. This way you get an “integrated” work tree while being organise changes in separate branches

GitButler 0.15 - "Quirky Quinceañera" GitButler 0.15 is out, featuring a brand new user interface, stability improvements, line based commits and more!

We just released v0.15 of the GitButler client - new layout, new UI, advanced commit message editor, partial hunk commits, uncommitting files, GitLab integration - so much going on in the last few months.
Check it out.
blog.gitbutler.com/gitbutler-15...

Oh nice! We should perhaps meet some time - beers on GitButler :)

Thanks for sharing this! Gonna take a look today. There is definitely room for improving the layout so this is helpful.

To add a little big more context - We are also working to re-enable allocating uncommitted changes to lanes, which prompts some further layout adjustments too.

Hey, sorry for the late reply here - been working really hard the past few days incorporating feedback. Here's how the app looks like on the latest nightly build.
More improvements are on the way too

Thank you for taking the time to share your feedback, Barry! 🙇‍♂️
I agree with you - something was lost in this transition. We are currently exploring options to bring back the lane view.

Stay tuned - the plan is to make a new release later this week so that we can gather another round of feedback.

It's not your fault - the app should do better. Currently, if the changes 'touch', GB treats it as if they intersected... which can lead to this kind of confusion.

Soon the app will allow partial committing (vid below) & it will be possible to handle this better. Thanks for being patient with us! 🙇‍♂️

GitButler Docs GitButler is a new Source Code Management system designed to manage your branches, record and backup your work, be your Git client, help with your code and much more

The reason for this is that the 'lanes' are meant to be 'peers' - independently apply-able branches. In the case where dependency is desired, GB has support for stacked branches:
docs.gitbutler.com/features/sta...

I am sorry for the confusion! In general, changes are "locked" because they depend on a preceding commit.

For example if you create a function and then commit it, and subsequently make a change to that function, that change is "locked" to the lane.

It only makes sense in the context of the commit

This is incredible! Just seeing it for the first time myself :)

20 years of Git. Still weird, still wonderful. Twenty years ago, Git was born. How did this unlikely "information manager" take over the world?

20 years ago today, Linus made the first commit on the Git project. Here is my birthday present post, looking back.

Happy birthday git, and thanks for all the fish.

blog.gitbutler.com/20-years-of-...

Release release/0.14.14 · gitbutlerapp/gitbutler What's Changed New features Adds a GitLab integration (docs: https://docs.gitbutler.com/features/gitlab-integration) Overhauled text editor for commit messages and PR/Review description introducin...

GitButler 0.14.14 is out!

New features:
- Adds a GitLab integration
- Overhauled text editor for commit messages
- Overhauled Pull Request / Review UI
- Adds syntax highlighting for additional languages
- ... and more 👇

Full notes github.com/gitbutlerapp...

I really enjoy working on @gitbutler.com illustrations! Here are some drafts and final versions for the "new branch" empty state. We actually reworked this, and now the whole section looks different 🥸

🤌

How Core Git Developers Configure Git What `git config` settings should be defaults by now? Here are some settings that even the core developers change.

PSA: everybody should set the git config `[branch] sort = -committerdate`, it should be the default tbh.

Though I am not sure about setting global git ignore, @scottchacon.com. I was once scratching my head why files were being ignored as I had forgotten about it blog.gitbutler.com/how-git-core...

Feel free to hit us up if you have any feature requests or run into a bug :)

"Are you a complicated Pull Request? Because you look good to me!"

I hear this is a good pick up line

This one is one of my all time favs. Should do a rewatch of it

Let's do it, I plan to be there

What are your thoughts on commit based review? (As opposed to branch based like PRs)

My pre-GitButler workflow was heavily relying on creating temp commits like "fu1", "fu2" etc and then "absorbing" those with rebase -i fixups :)

It's all obsolete now that i get to just drag to absorb/amend with the butler 😅

That part was truly terrifying!

btw - you skipped the most useful interactive command - fixup ;)

Oh this is really insightful, thanks for sharing. Working on @gitbutler.com, something that has been tricky are commit hooks on Mac because of the env situation. I will try out something like what you describe in 1)!

If you do end up trying it in your workflow, do let us know how it goes. I’d love to nail all the corner cases around this use case.

Are you referring to the discourse on Twitter? I believe tweets that contain “Bluesky” are in some way suppressed

Stacked Branches with GitButler GitButler can now manage dependent branches that are stacked, including managing stacked GitHub PRs.

GitButler 0.14 is out, now with our long-awaited stacked branches feature. Check it out!

blog.gitbutler.com/stacked-bran...

Hey! I am really sorry about this shitty experience... I would love to fix this asap - what do you mean by the original authors being pinged?