Jesse Duffield 595e28d335 Support bare worktrees where worktree does not have its own .git file ... This was on oversight on my part: I assumed that the --work-tree arg was always intended for use with linked worktrees which have a .git file pointing back to the repo. I'm honestly confused now: seems like there are three kinds of worktrees: * the main worktree of a non-bare repo * a linked worktree (with its own gitdir in the repo's worktrees/ dir) * a random folder which you specify as a worktree with the --work-tree arg I'm pretty sure the --work-tree arg is only intended to be used with this third kind or workree		2023-08-07 22:40:53 +10:00
..
git_commands	Support bare worktrees where worktree does not have its own .git file	2023-08-07 22:40:53 +10:00
git_config	Remove secureexec package	2023-07-30 19:59:51 +10:00
hosting_service	Standardise on using lo for slice functions	2023-07-30 18:51:23 +10:00
models	Use fields rather than methods on worktrees	2023-07-30 18:35:24 +10:00
oscommands	Appease linter	2023-08-02 08:32:57 +10:00
patch	Standardise on using lo for slice functions	2023-07-30 18:51:23 +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	Write unit tests with the help of afero	2023-07-30 18:35:36 +10:00
git.go	Write unit tests with the help of afero	2023-07-30 18:35:36 +10:00