CLI apply reports success but leaves outdated branch unapplied

[sciyoshi]

Version

but 0.5.2053

Operating System

macOS 26.5, Apple Silicon

Distribution Method

Nightly / CLI

Describe the issue

When applying an older local branch with but apply, the CLI can report success even though the branch remains unapplied and is not added to the workspace commit.

The command exits with status 0 and prints a success message:

Applied branch 'feature/outdated-branch' to workspace

However, checking afterward shows that the branch is still listed under unapplied branches and is absent from the applied workspace state.

How to reproduce

I do not have a minimal public repository yet, but this reproduced in a repository with several applied virtual branches and one older, non-updated local branch.

1. Start with a GitButler workspace that has multiple applied branches.
2. Have an older local branch, e.g. feature/outdated-branch, that is listed under Unapplied Branches by but branch list.
3. Run:

but apply feature/outdated-branch

4. Observe the command output:

Applied branch 'feature/outdated-branch' to workspace

5. Run:

but branch list
but status -fv
git log --oneline --decorate --graph --max-count=12 gitbutler/workspace

Actual behavior

but apply exits successfully and prints that the branch was applied, but:

• but branch list still shows feature/outdated-branch under Unapplied Branches
• but status -fv does not show the branch in the workspace
• gitbutler/workspace does not include the branch

Expected behavior

Either:

• the branch is actually applied to the workspace, or
• the command exits non-zero and reports why it could not apply the branch, such as conflicts, branch needing update, or another workspace state issue

Notes

This may be related to existing apply/conflict handling issues, but the confusing part here is specifically the CLI success message and zero exit status when the branch remains unapplied.

[slarse]

Hi @sciyoshi,

Thanks for the report! This is a known issue that we've got pegged for fixing in the not too distant future. Can't give an ETA as we've currently got higher priority items in the CLI, but it should get fixed soon-ish :)