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
..
daemon	Remove secureexec package	2023-07-30 19:59:51 +10:00
types	move code from main into app package to allow test to be injected	2022-08-13 13:55:08 +10:00
app.go	Standardise on using lo for slice functions	2023-07-30 18:51:23 +10:00
entry_point.go	Support bare worktrees where worktree does not have its own .git file	2023-08-07 22:40:53 +10:00
errors.go	Standardise on using lo for slice functions	2023-07-30 18:51:23 +10:00