4 commits

Author	SHA1	Message	Date
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
Jesse Duffield	4c5b1574f1	Centralise logic for obtaining repo paths ... There are quite a few paths you might want to get e.g. the repo's path, the worktree's path, the repo's git dir path, the worktree's git dir path. I want these all obtained once and then used when needed rather than having to have IO whenever we need them. This is not so much about reducing time spent on IO as it is about not having to care about errors every time we want a path.	2023-07-30 18:35:24 +10:00
Jesse Duffield	cd5b041b0f	clearer separation of concerns when bootstrapping application	2022-05-07 16:02:04 +10:00
Jesse Duffield	75598ea2a1	move git dir env stuff into a centralised package	2020-09-29 17:42:07 +10:00