Scott Chacon
Scott Chacon
It would be nice to see when you ran an absorb, rather than just the `CreateCommit` entries: ``` ❯ but st took 5s ╭┄00 [Unassigned Changes] ┊ rv M config/routes.rb...
Similar to [#11102](https://github.com/gitbutlerapp/gitbutler/issues/11102), GitButler has an "edit mode" where you can essentially checkout a single commit (something like detached HEAD), make whatever changes you want and then pop back out...
Currently there is no way to go into resolution mode from the CLI, only the GUI. Let's say we have a conflict at the bottom of our commit stack: ```...
Instead of this: ``` ❯ but worktree new sc-branch-74 Preparing worktree (new branch 'gitbutler/worktree/7c67c2c6-4044-43e2-b88f-4b80e661b5ce') Created worktree at: /Users/schacon/projects/gitbutler/.git/gitbutler/worktrees/7c67c2c6-4044-43e2-b88f-4b80e661b5ce Reference: refs/heads/sc-branch-74 ``` Perhaps this (with some colors for the new branch...
I tried to create three file changes that were locked to three different branches and `absorb` bailed. ``` ❯ but stf ╭┄00 [Unassigned Changes] ┊ nx M Gemfile 🔒 427019e...
Would be nice to have a verbose debugging mode. ``` $ but -v rub m6 my-branch # Verbose output: # Resolving source 'm6'... found file 'test.md' # Resolving target 'my-branch'......
Problem: Can't use filenames directly in but rub - they're parsed as range syntax. Reproduction: ``` $ but rub test-simple.md my-branch Error: Start of range 'test' must match exactly one...
Worktrees are different than virtual branches - you can't have virtual branches in a worktree (we don't want cascading virtual branches), but we want to still use the `but` commands,...
The `but absorb` command is pretty magical, it would be nice to have it describe exactly what it's deciding to do and why it's deciding to do it. ``` ❯...
It would be nice to have a CLI way to do what the mcp server does - take the work in progress, a prompt and create a commit message for...