Stefan Haller a75b0457c1 Ask before discarding a nested repository if that loses anything ...

Discarding a nested repository deletes its directory like that of any
untracked file. If the repository keeps its git dir in its directory,
this deletes all of its history, and nothing said so. The directory of
a removed submodule keeps its git dir elsewhere, but it may have
changes that aren't committed.

Check for both before discarding. If anything would be lost, list it
and ask for confirmation.

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

2026-10-15 20:51:34 +02:00

..

direnv

Offer direnv .envrc approval from inside lazygit

2026-06-04 09:05:01 +02:00

git_commands

Ask before discarding a nested repository if that loses anything

2026-10-15 20:51:34 +02:00

git_config

Pin the cached git config's commands to the repo directory

2026-07-20 17:07:39 +02:00

hosting_service

Optimize regex compilations

2026-05-10 15:28:14 +02:00

models

Don't stage nested repositories

2026-10-15 20:51:34 +02:00

oscommands

Restore the terminal if a goroutine panics

2026-10-14 20:28:53 +02:00

patch

Number the lines of a patch in one pass when indexing its change lines

2026-10-14 08:41:50 +02:00

testdata

Support opening lazygit in a submodule

2019-05-12 17:59:49 +10:00

git_cmd_obj_builder_test.go

Tell git where the repo is when it can't find it itself

2026-08-08 11:15:01 +02:00

git_cmd_obj_builder.go

Tell git where the repo is when it can't find it itself

2026-08-08 11:15:01 +02:00

git_cmd_obj_runner_test.go

Back off exponentially between lock-error retries

2026-07-15 10:08:44 +02:00

git_cmd_obj_runner.go

Back off exponentially between lock-error retries

2026-07-15 10:08:44 +02:00

git.go

Materialize the custom patch so the diff renderer can show it

2026-10-05 11:33:11 +02:00