Version
v0.22.3
Operating System
Linux
Describe the issue
Unless you literally use GitButler with every single project on your machine, installing skills globally is almost always going to make a mess, agents get super confused, start to randomly convert projects to GitButler or commit things in weird ways, etc.
I realize local also might also have its issues if you work in a team and commit it and your team isn't all-in on GitButler, but the 'global' setting just feels like a huge footgun to me. The two options should be imho:
- Local (commit to repo)
- Local (only for me, gitignore the GitButler skill so only I see it)
Activity
6
krlvi28d agoOne thing we are doing is working on removing the root cause of the foot gun - the inability for gitbutler to work in a normal repo without converting it: https://github.com/gitbutlerapp/gitbutler/issues/11866
If you are on the nightly, there is a feature flag u can set in ~/.config/gitbutler/settings.json
{
"featureFlags": {
"singleBranch": true
}
}With this setting on, the app will behave like a normal git client until parallel branches are requested. The feature is nearly ready for GA (2 more weeks or so)
anaisbetts25d agoThe skill should only describe how to use gitbutler and not tell the AI that it's a git replacement that should always be used. That way you can install it globally without any issue.
Unfortunately that doesn't seem to be the case at least in my experience, models don't always get the nuance then proceed to get wedged, it's quite a bad experience if you have many Git repos that aren't managed by GitButler.
boyvinall24d agoworkaround, my ~/.claude/CLAUDE.md says:
- git operations should only use gitbutler if the repository has already been setup for that. Do not
run `but setup` on any repository unless explicitly requested.
veber-alex24d agoworkaround, my
~/.claude/CLAUDE.mdsays:- git operations should only use gitbutler if the repository has already been setup for that. Do not run `but setup` on any repository unless explicitly requested.
This is exactly what should be part of the skill
slarse11d ago6. > workaround, my
~/.claude/CLAUDE.mdsays: >> - git operations should only use gitbutler if the repository has already been setup for that. Do not > run `but setup` on any repository unless explicitly requested. >This is exactly what should be part of the skill
It's not necessary anymore, but setup has been removed in nightly and will not be part of the next release. We have simply done away with the need for it. Like @krlvi mentioned above, the latest work on but makes it simply work in Git repositories without requiring any setup prior to running any commands.
An agent can run commands with but and then with git and they work seamlessly together so long as you don't checkout parallel branches with but.
The skill should only describe how to use gitbutler and not tell the AI that it's a git replacement that should always be used. That way you can install it globally without any issue. After that you can use project local file like CLAUDE.md (entire team) or CLAUDE.local.md (only you) to tell the AI that this project is managed by gitbutler.