Hi!
I noticed a potential bug with the invocation of a pre-commit hook
when running git with --work-tree and --git-dir. In particular, I was
investigating how hooks can still run git commands properly even when
the work-tree or git-dir is overridden via CLI args. I put the
following in "/home/mgsloan/.dotfiles-git/hooks/pre-commit":
#!/bin/sh
env
after this, running "git --work-tree=/home/mgsloan
--git-dir=/home/mgsloan/.dotfiles-git commit" has output with a bunch
of variables, here are the important ones:
GIT_WORK_TREE=.
GIT_DIR=.dotfiles-git/
PWD=/home/mgsloan
So what's the problem with this choice of environment variables?
Well, the problem is that if PWD is changed during the execution of
the script, then GIT_WORK_TREE and GIT_DIR will no longer work
properly. For example, if the pre-commit hook is
#!/bin/sh
cd some-dir
git status
This will fail with
Not a git repository: '.dotfiles-git'
There is another detail here, which is that when --git-dir /
--work-tree is not specified, the no GIT_WORK_TREE / GIT_DIR
environment variable is set. This means that in this case, changing
PWD in the hook will work fine as long as the search for .git will
find the right one. Note that this also means that changing PWD in a
script can change which git repo the command is being run on, for
example, when the hook is interacting with a submodule.
A half-fix to this would be to have the GIT_WORK_TREE and GIT_DIR set
when running hooks use absolute paths. However, this would not have
the same behavior as when git is used without --git-dir / --work-tree.
As described in the paragraph above, if PWD is relied upon to instead
target a different git repo, then things break.
Not sure what the total fix for this would be. I think the
information that needs to be conveyed to the hook's git invocations is
that "the work-tree /home/mgsloan should be associated with the
git-dir /home/mgsloan/.dotfiles-git". Could have an env var like
GIT_DIR_MAPPINGS="/home/mgsloan!/home/mgsloan/.dotfiles-git"
The idea is that this would be a list of mappings from GIT_WORK_TREE
to GIT_DIR. If this variable is set, then it will be followed when
git is searching parents of PWD for ".git" directories. I chose "!"
rather arbitrarily here. "->" would look nicer, but people might
forget to escape it when programmatically setting this var.
What do y'all think of this idea?
Some of you might be wondering what I'm doing with my work tree being
my home directory. It is the approach suggested here -
https://developer.atlassian.com/blog/2016/02/best-way-to-store-dotfiles-git-bare-repo/
- for versioning your configuration files directly.
Apologies if this has already been discussed, I could not find a good
way to search the mailinglist archives.
Thanks!
-Michael
