Jesse Duffield 63dc07fded Construct arg vector manually rather than parse string ... By constructing an arg vector manually, we no longer need to quote arguments Mandate that args must be passed when building a command Now you need to provide an args array when building a command. There are a handful of places where we need to deal with a string, such as with user-defined custom commands, and for those we now require that at the callsite they use str.ToArgv to do that. I don't want to provide a method out of the box for it because I want to discourage its use. For some reason we were invoking a command through a shell when amending a commit, and I don't believe we needed to do that as there was nothing user- supplied about the command. So I've switched to using a regular command out- side the shell there		2023-05-23 19:49:19 +10:00
..
git_commands	Construct arg vector manually rather than parse string	2023-05-23 19:49:19 +10:00
git_config	remove deprecated calls	2022-09-17 15:10:41 -07:00
hosting_service	feat: add gitea to hosting service	2023-04-18 16:16:09 +00:00
models	Store commit.Action as an enum instead of a string	2023-04-15 08:36:03 +02:00
oscommands	Construct arg vector manually rather than parse string	2023-05-23 19:49:19 +10:00
patch	Refactor interface for ApplyPatch	2023-05-20 20:54:39 +10:00
testdata	Support opening lazygit in a submodule	2019-05-12 17:59:49 +10:00
types/enums	more refactoring	2022-01-04 09:07:15 +11:00
git.go	Construct arg vector manually rather than parse string	2023-05-23 19:49:19 +10: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	fix(loaders/file.go): changed to ignore stderr when loading git status	2022-09-19 18:46:32 +09:00
git_test.go	feat: add GitVersion struct	2022-12-30 20:01:14 +09:00