Jesse Duffield 429225da80 Support random order of command execution in unit tests ... Now that we run code concurrently in our loaders, we need to handle that in our tests. We could enforce a deterministic ordering by mocking waitgroup or something like that, but I think it's fine to let our tests handle some randomness given that prod itself will have that randomness. I've removed the patch test file because it was clunky, not providing much value, and it would have been hard to refactor to the new pattern		2023-07-29 12:36:17 +10:00
..
git_commands	Support random order of command execution in unit tests	2023-07-29 12:36:17 +10:00
git_config	Use mutex on cached git config	2023-07-09 21:30:19 +10:00
hosting_service	Update gitlab commit URL to match new routing	2023-05-22 07:39:47 +03:30
models	Keep track of authors across local commits and branch commits for suggestions	2023-07-22 10:47:04 +10:00
oscommands	Support random order of command execution in unit tests	2023-07-29 12:36:17 +10:00
patch	Refactor interface for ApplyPatch	2023-05-20 20:54:39 +10:00
testdata
types/enums	more refactoring	2022-01-04 09:07:15 +11:00
git_cmd_obj_builder.go	Construct arg vector manually rather than parse string	2023-05-23 19:49:19 +10:00
git_cmd_obj_runner.go	Retry on index.lock error	2023-07-10 19:13:18 +10:00
git_test.go	feat: add GitVersion struct	2022-12-30 20:01:14 +09:00
git.go	Use comment char config on interactive rebase	2023-07-02 02:07:32 -03:00