Skip to content

Commit e2eb527

Browse files
committed
require-work-tree wants more than what its name says
Somebody tried "git pull" from a random place completely outside the work tree, while exporting GIT_DIR and GIT_WORK_TREE that are set to correct places, e.g. GIT_WORK_TREE=$HOME/git.git GIT_DIR=$GIT_WORK_TREE/.git export GIT_WORK_TREE GIT_DIR cd /tmp git pull At the beginning of git-pull, we check "require-work-tree" and then "cd-to-toplevel". I _think_ the original intention when I wrote the command was "we MUST have a work tree, our $(cwd) might not be at the top-level directory of it", and no stronger than that. That check is a very sensible thing to do before doing cd-to-toplevel. We check that the place we would want to go exists, and then go there. But the implementation of require_work_tree we have today is quite different. I don't have energy to dig the history, but currently it says: test "$(git rev-parse --is-inside-work-tree 2>/dev/null)" = true || die "fatal: $0 cannot be used without a working tree." Which is completely bogus. Even though we may happen to be just outside of it right now, we may have a working tree that we can cd_to_toplevel back to. Add a function "require_work_tree_exists" that implements the check this function originally intended (this is so that third-party scripts that rely on the current behaviour do not have to get broken). For now, update _no_ in-tree scripts, not even "git pull", as nobody on the list seems to really care about the above corner case workflow that triggered this. Scripts can be updated after vetting that they do want the "we want to make sure the place we are going to go actually exists" semantics. Signed-off-by: Junio C Hamano <[email protected]>
1 parent 7ed863a commit e2eb527

File tree

2 files changed

+15
-3
lines changed

2 files changed

+15
-3
lines changed

Documentation/git-sh-setup.txt

Lines changed: 8 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -58,9 +58,14 @@ cd_to_toplevel::
5858
runs chdir to the toplevel of the working tree.
5959

6060
require_work_tree::
61-
checks if the repository is a bare repository, and dies
62-
if so. Used by scripts that require working tree
63-
(e.g. `checkout`).
61+
checks if the current directory is within the working tree
62+
of the repository, and otherwise dies.
63+
64+
require_work_tree_exists::
65+
checks if the working tree associated with the repository
66+
exists, and otherwise dies. Often done before calling
67+
cd_to_toplevel, which is impossible to do if there is no
68+
working tree.
6469

6570
get_author_ident_from_commit::
6671
outputs code for use with eval to set the GIT_AUTHOR_NAME,

git-sh-setup.sh

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -140,6 +140,13 @@ cd_to_toplevel () {
140140
}
141141
}
142142
143+
require_work_tree_exists () {
144+
if test "z$(git rev-parse --is-bare-repository)" != zfalse
145+
then
146+
die "fatal: $0 cannot be used without a working tree."
147+
fi
148+
}
149+
143150
require_work_tree () {
144151
test "$(git rev-parse --is-inside-work-tree 2>/dev/null)" = true ||
145152
die "fatal: $0 cannot be used without a working tree."

0 commit comments

Comments
 (0)