Stefan Haller 785c8a712c Explain when a submodule has nothing stageable ...

A submodule that only has dirty or untracked content (no new commit) can't
be staged from the parent repo, but it still shows up as having unstaged
changes. Pressing stage on it therefore briefly flashed as staged and then
reverted, without explaining why nothing was staged.

Detect this case (via `git submodule status`, where a '+' prefix marks a
stageable commit change) in the shared stage/unstage decision: if the only
thing that looks stageable is such a submodule, don't try to stage it.
Instead unstage if there's anything staged to unstage, so the toggle stays
symmetric; otherwise show an error explaining that there's nothing to stage.

Because the decision is shared, this covers both the stage (space) and
stage-all (a) keybindings.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

2026-06-04 09:12:09 +02:00

..

add.go

…

enter_nested.go

…

enter.go

Convert custom command Key fields to Keybinding

2026-05-25 15:32:47 +02:00

remove_nested.go

…

remove.go

…

reset_folder.go

…

reset.go

Convert custom command Key fields to Keybinding

2026-05-25 15:32:47 +02:00

shared.go

…

stage_all_with_dirty_submodule.go

Explain when a submodule has nothing stageable

2026-06-04 09:12:09 +02:00

stage_dirty_only.go

Explain when a submodule has nothing stageable

2026-06-04 09:12:09 +02:00

stage.go

Also verify stage-all can unstage a dirty submodule

2026-06-04 09:12:09 +02:00