2009-10-12 13:27:04 +08:00
|
|
|
#!/bin/sh
|
|
|
|
|
|
|
|
test_description='Test git check-ref-format'
|
|
|
|
|
|
|
|
. ./test-lib.sh
|
|
|
|
|
|
|
|
valid_ref() {
|
|
|
|
test_expect_success "ref name '$1' is valid" \
|
|
|
|
"git check-ref-format '$1'"
|
|
|
|
}
|
|
|
|
invalid_ref() {
|
|
|
|
test_expect_success "ref name '$1' is not valid" \
|
|
|
|
"test_must_fail git check-ref-format '$1'"
|
|
|
|
}
|
|
|
|
|
|
|
|
valid_ref 'heads/foo'
|
|
|
|
invalid_ref 'foo'
|
|
|
|
valid_ref 'foo/bar/baz'
|
|
|
|
valid_ref 'refs///heads/foo'
|
|
|
|
invalid_ref 'heads/foo/'
|
check-ref-format --print: Normalize refnames that start with slashes
When asked if "refs///heads/master" is valid, check-ref-format says "Yes,
it is well formed", and when asked to print canonical form, it shows
"refs/heads/master". This is so that it can be tucked after "$GIT_DIR/"
to form a valid pathname for a loose ref, and we normalize a pathname like
"$GIT_DIR/refs///heads/master" to de-dup the slashes in it.
Similarly, when asked if "/refs/heads/master" is valid, check-ref-format
says "Yes, it is Ok", but the leading slash is not removed when printing,
leading to "$GIT_DIR//refs/heads/master".
Fix it to make sure such leading slashes are removed. Add tests that such
refnames are accepted and normalized correctly.
Signed-off-by: Michael Haggerty <mhagger@alum.mit.edu>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2011-08-26 03:19:24 +08:00
|
|
|
valid_ref '/heads/foo'
|
|
|
|
valid_ref '///heads/foo'
|
|
|
|
invalid_ref '/foo'
|
2009-10-12 13:27:04 +08:00
|
|
|
invalid_ref './foo'
|
|
|
|
invalid_ref '.refs/foo'
|
|
|
|
invalid_ref 'heads/foo..bar'
|
|
|
|
invalid_ref 'heads/foo?bar'
|
|
|
|
valid_ref 'foo./bar'
|
|
|
|
invalid_ref 'heads/foo.lock'
|
|
|
|
valid_ref 'heads/foo@bar'
|
|
|
|
invalid_ref 'heads/v@{ation'
|
|
|
|
invalid_ref 'heads/foo\bar'
|
2011-08-27 12:12:44 +08:00
|
|
|
invalid_ref "$(printf 'heads/foo\t')"
|
|
|
|
invalid_ref "$(printf 'heads/foo\177')"
|
|
|
|
valid_ref "$(printf 'heads/fu\303\237')"
|
2009-10-12 13:27:04 +08:00
|
|
|
|
|
|
|
test_expect_success "check-ref-format --branch @{-1}" '
|
|
|
|
T=$(git write-tree) &&
|
|
|
|
sha1=$(echo A | git commit-tree $T) &&
|
|
|
|
git update-ref refs/heads/master $sha1 &&
|
2010-10-31 09:46:54 +08:00
|
|
|
git update-ref refs/remotes/origin/master $sha1 &&
|
2009-10-12 13:27:04 +08:00
|
|
|
git checkout master &&
|
|
|
|
git checkout origin/master &&
|
|
|
|
git checkout master &&
|
|
|
|
refname=$(git check-ref-format --branch @{-1}) &&
|
|
|
|
test "$refname" = "$sha1" &&
|
|
|
|
refname2=$(git check-ref-format --branch @{-2}) &&
|
|
|
|
test "$refname2" = master'
|
|
|
|
|
2010-08-06 11:39:22 +08:00
|
|
|
test_expect_success 'check-ref-format --branch from subdir' '
|
|
|
|
mkdir subdir &&
|
|
|
|
|
|
|
|
T=$(git write-tree) &&
|
|
|
|
sha1=$(echo A | git commit-tree $T) &&
|
|
|
|
git update-ref refs/heads/master $sha1 &&
|
2010-10-31 09:46:54 +08:00
|
|
|
git update-ref refs/remotes/origin/master $sha1 &&
|
2010-08-06 11:39:22 +08:00
|
|
|
git checkout master &&
|
|
|
|
git checkout origin/master &&
|
|
|
|
git checkout master &&
|
|
|
|
refname=$(
|
|
|
|
cd subdir &&
|
|
|
|
git check-ref-format --branch @{-1}
|
|
|
|
) &&
|
|
|
|
test "$refname" = "$sha1"
|
|
|
|
'
|
|
|
|
|
2009-10-13 07:39:43 +08:00
|
|
|
valid_ref_normalized() {
|
|
|
|
test_expect_success "ref name '$1' simplifies to '$2'" "
|
|
|
|
refname=\$(git check-ref-format --print '$1') &&
|
|
|
|
test \"\$refname\" = '$2'"
|
|
|
|
}
|
|
|
|
invalid_ref_normalized() {
|
|
|
|
test_expect_success "check-ref-format --print rejects '$1'" "
|
|
|
|
test_must_fail git check-ref-format --print '$1'"
|
|
|
|
}
|
|
|
|
|
|
|
|
valid_ref_normalized 'heads/foo' 'heads/foo'
|
|
|
|
valid_ref_normalized 'refs///heads/foo' 'refs/heads/foo'
|
check-ref-format --print: Normalize refnames that start with slashes
When asked if "refs///heads/master" is valid, check-ref-format says "Yes,
it is well formed", and when asked to print canonical form, it shows
"refs/heads/master". This is so that it can be tucked after "$GIT_DIR/"
to form a valid pathname for a loose ref, and we normalize a pathname like
"$GIT_DIR/refs///heads/master" to de-dup the slashes in it.
Similarly, when asked if "/refs/heads/master" is valid, check-ref-format
says "Yes, it is Ok", but the leading slash is not removed when printing,
leading to "$GIT_DIR//refs/heads/master".
Fix it to make sure such leading slashes are removed. Add tests that such
refnames are accepted and normalized correctly.
Signed-off-by: Michael Haggerty <mhagger@alum.mit.edu>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2011-08-26 03:19:24 +08:00
|
|
|
valid_ref_normalized '/heads/foo' 'heads/foo'
|
|
|
|
valid_ref_normalized '///heads/foo' 'heads/foo'
|
2009-10-13 07:39:43 +08:00
|
|
|
invalid_ref_normalized 'foo'
|
check-ref-format --print: Normalize refnames that start with slashes
When asked if "refs///heads/master" is valid, check-ref-format says "Yes,
it is well formed", and when asked to print canonical form, it shows
"refs/heads/master". This is so that it can be tucked after "$GIT_DIR/"
to form a valid pathname for a loose ref, and we normalize a pathname like
"$GIT_DIR/refs///heads/master" to de-dup the slashes in it.
Similarly, when asked if "/refs/heads/master" is valid, check-ref-format
says "Yes, it is Ok", but the leading slash is not removed when printing,
leading to "$GIT_DIR//refs/heads/master".
Fix it to make sure such leading slashes are removed. Add tests that such
refnames are accepted and normalized correctly.
Signed-off-by: Michael Haggerty <mhagger@alum.mit.edu>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2011-08-26 03:19:24 +08:00
|
|
|
invalid_ref_normalized '/foo'
|
2009-10-13 07:39:43 +08:00
|
|
|
invalid_ref_normalized 'heads/foo/../bar'
|
|
|
|
invalid_ref_normalized 'heads/./foo'
|
|
|
|
invalid_ref_normalized 'heads\foo'
|
|
|
|
|
2009-10-12 13:27:04 +08:00
|
|
|
test_done
|