1
0
Fork 0
mirror of https://github.com/git/git.git synced 2024-11-05 08:47:56 +01:00
git/t/t5600-clone-fail-cleanup.sh
Yasushi SHOJI ced78b3907 clone: the given repository dir should be relative to $PWD
the repository argument for git-clone should be relative to $PWD
instead of the given target directory.  The old behavior gave us
surprising success and you need a few minute to know why it worked.

GIT_DIR is already exported so no need to cd into $D. And this makes
$PWD for git-fetch-pack, which is the actual command to take the given
repository dir, the same as git-clone.

Signed-off-by: Yasushi SHOJI <yashi@atmark-techno.com>
Signed-off-by: Junio C Hamano <junkio@cox.net>
2006-10-14 18:22:04 -07:00

42 lines
1.1 KiB
Bash
Executable file

#!/bin/sh
#
# Copyright (C) 2006 Carl D. Worth <cworth@cworth.org>
#
test_description='test git-clone to cleanup after failure
This test covers the fact that if git-clone fails, it should remove
the directory it created, to avoid the user having to manually
remove the directory before attempting a clone again.'
. ./test-lib.sh
test_expect_failure \
'clone of non-existent source should fail' \
'git-clone foo bar'
test_expect_failure \
'failed clone should not leave a directory' \
'cd bar'
# Need a repo to clone
test_create_repo foo
# clone doesn't like it if there is no HEAD. Is that a bug?
(cd foo && touch file && git add file && git commit -m 'add file' >/dev/null 2>&1)
# source repository given to git-clone should be relative to the
# current path not to the target dir
test_expect_failure \
'clone of non-existent (relative to $PWD) source should fail' \
'git-clone ../foo baz'
test_expect_success \
'clone should work now that source exists' \
'git-clone foo bar'
test_expect_success \
'successfull clone must leave the directory' \
'cd bar'
test_done