Stefan Haller 8b049be31d Find the lazygit root directory by go.mod instead of .git ... Running the tests in an exported source tarball fails with "must run in lazy project folder or child folder". GetLazyRootDirectory searches the working directory and its parents for a .git directory, and a tarball doesn't have one. This has always affected the integration tests; since 34da956f5d a unit test calls the function too, so now even `go test ./... -short` fails. Search for the go.mod file that declares lazygit's module instead. It ships in tarballs, and there is exactly one of it per source tree. Put the function in our own pkg/utils rather than change lazycore's; the criterion is specific to lazygit, and I don't feel like making a change to lazycore. Return an error rather than call log.Fatal, and report it from the two callers that run under `go test`. In a test binary, log.Fatal exits without attributing the failure to any test. That is the failure mode 34da956f5d set out to remove. The remaining callers are development tools that have nothing useful to do without the root directory; they keep exiting, now through MustFindLazygitRootDirectory. Also stop the search at the root of the file system rather than at "/". On Windows the old loop walks up to "C:\" and then spins there forever.		2026-09-09 09:27:44 +02:00
..
yaml_utils
color.go
color_test.go
date.go
date_test.go
dummies.go
errors.go
formatting.go
formatting_test.go
history_buffer.go
history_buffer_test.go
io.go
io_test.go
lines.go
lines_test.go
once_writer.go
once_writer_test.go
project_root.go	Find the lazygit root directory by go.mod instead of .git	2026-09-09 09:27:44 +02:00
project_root_test.go	Find the lazygit root directory by go.mod instead of .git	2026-09-09 09:27:44 +02:00
rebase_todo.go
rebase_todo_test.go
regexp.go
regexp_test.go
search.go
search_test.go
slice.go
slice_test.go
stack.go
string_pool.go
template.go
template_test.go
thread_safe_map.go
thread_safe_map_test.go
utils.go
utils_test.go