I have observed that as the context gets filled, Claude starts forgetting things. One silly “trick” is to have a hook which reminds it what it needs to do but tbh it habituates and after some time it starts ignoring that as well. It needs to be fed novel info to work
Codex or Claude? There are some tricks we are working on to make agents handle this better
⋈❤️🐧 You can now install the `but` CLI on Linux!
gitbutler.com/cli
fwiw, we love what we do
Incredibly proud of what the team just shipped! ❤️ GitButler now officially has a CLI 👾
So happy and grateful to have you onboard Oliver 🙇♂️! Exciting things to come, in the VCS & devtools space!
Cursor (lifecycle) Hooks just dropped and GitButler already has support for it!
Thank you Cursor team for the early access! Check out what we built with it blog.gitbutler.com/cursor-hooks...
This Claude UI design by @pavellaptev.bsky.social is absolute 🚀
Hey! Thanks for the shout-out! Just wanted to clarify that GB's virtual branches dont use multiple worktrees but instead utilizes a managed reference where the branches are continuously integrated with an octopus merge on top to simulate one integrated branch :)
Working very hard right now to squash all of them bugs! Sorry for the inconvenience
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
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! 🙇♂️
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 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-...
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 🥸
🤌
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
