Stefan Haller c588c5507c Add a test demonstrating that you can't unstage a dirty submodule ... When a submodule has both a new commit (which the parent repo can stage) and dirty working-tree content (which it can't), staging it lands on a "MM" status. Pressing space again should unstage it, but instead it tries to stage the dirty content over and over, so you can never get back to an unstaged state. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>		2026-06-04 09:12:09 +02:00
..
add.go	Add a root item ("/") if files at top level have changed	2025-03-21 08:04:58 +01:00
enter.go	Convert custom command Key fields to Keybinding	2026-05-25 15:32:47 +02:00
enter_nested.go	Remove conditional code related to git earlier than 2.22	2025-04-09 10:40:52 +02:00
remove.go	Add integration test	2025-04-07 09:42:19 +02:00
remove_nested.go	Make file sort order and case sensitivity configurable	2026-03-30 17:53:25 +02:00
reset.go	Convert custom command Key fields to Keybinding	2026-05-25 15:32:47 +02:00
reset_folder.go	Update disabled message	2025-04-07 09:42:19 +02:00
shared.go	Show all submodules recursively	2024-03-07 20:16:28 +01:00
stage.go	Add a test demonstrating that you can't unstage a dirty submodule	2026-06-04 09:12:09 +02:00