Jesse Duffield 16ed3c2377 Retry on index.lock error ... I don't know why we're getting index.lock errors but they're impossile to stop anyway given that other processes can be calling git commands. So we're retrying a few times before re-raising. To do this we need to clone the command and the current implementation for that is best-effort. I do worry about the maintainability of that but we'll see how it goes. Also, I thought you'd need to clone the task (if it exists) but now I think not; as long as you don't call done twice on it you should be fine, and you shouldn't be done'ing a task as part of running a command: that should happen higher up.		2023-07-10 19:13:18 +10:00
..
dir_with_untracked_file.go	Construct arg vector manually rather than parse string	2023-05-23 19:49:19 +10:00
discard_all_dir_changes.go	Add integration tests for discarding files	2023-07-03 12:54:13 +10:00
discard_changes.go	Retry on index.lock error	2023-07-10 19:13:18 +10:00
discard_staged_changes.go	Use sentence case everywhere	2023-05-25 23:52:19 +10:00
discard_unstaged_dir_changes.go	Add integration tests for discarding files	2023-07-03 12:54:13 +10:00
discard_unstaged_file_changes.go	Add integration tests for discarding files	2023-07-03 12:54:13 +10:00
gitignore.go	Use sentence case everywhere	2023-05-25 23:52:19 +10:00
remember_commit_message_after_fail.go	Use sentence case everywhere	2023-05-25 23:52:19 +10:00