2012-11-28 22:11:01 +00:00
|
|
|
#!/bin/sh
|
|
|
|
#
|
|
|
|
# Copyright (c) 2010 Sverre Rabbelier
|
|
|
|
#
|
|
|
|
|
|
|
|
test_description='Test remote-helper import and export commands'
|
|
|
|
|
2020-11-18 23:44:35 +00:00
|
|
|
GIT_TEST_DEFAULT_INITIAL_BRANCH_NAME=main
|
tests: mark tests relying on the current default for `init.defaultBranch`
In addition to the manual adjustment to let the `linux-gcc` CI job run
the test suite with `master` and then with `main`, this patch makes sure
that GIT_TEST_DEFAULT_INITIAL_BRANCH_NAME is set in all test scripts
that currently rely on the initial branch name being `master by default.
To determine which test scripts to mark up, the first step was to
force-set the default branch name to `master` in
- all test scripts that contain the keyword `master`,
- t4211, which expects `t/t4211/history.export` with a hard-coded ref to
initialize the default branch,
- t5560 because it sources `t/t556x_common` which uses `master`,
- t8002 and t8012 because both source `t/annotate-tests.sh` which also
uses `master`)
This trick was performed by this command:
$ sed -i '/^ *\. \.\/\(test-lib\|lib-\(bash\|cvs\|git-svn\)\|gitweb-lib\)\.sh$/i\
GIT_TEST_DEFAULT_INITIAL_BRANCH_NAME=master\
export GIT_TEST_DEFAULT_INITIAL_BRANCH_NAME\
' $(git grep -l master t/t[0-9]*.sh) \
t/t4211*.sh t/t5560*.sh t/t8002*.sh t/t8012*.sh
After that, careful, manual inspection revealed that some of the test
scripts containing the needle `master` do not actually rely on a
specific default branch name: either they mention `master` only in a
comment, or they initialize that branch specificially, or they do not
actually refer to the current default branch. Therefore, the
aforementioned modification was undone in those test scripts thusly:
$ git checkout HEAD -- \
t/t0027-auto-crlf.sh t/t0060-path-utils.sh \
t/t1011-read-tree-sparse-checkout.sh \
t/t1305-config-include.sh t/t1309-early-config.sh \
t/t1402-check-ref-format.sh t/t1450-fsck.sh \
t/t2024-checkout-dwim.sh \
t/t2106-update-index-assume-unchanged.sh \
t/t3040-subprojects-basic.sh t/t3301-notes.sh \
t/t3308-notes-merge.sh t/t3423-rebase-reword.sh \
t/t3436-rebase-more-options.sh \
t/t4015-diff-whitespace.sh t/t4257-am-interactive.sh \
t/t5323-pack-redundant.sh t/t5401-update-hooks.sh \
t/t5511-refspec.sh t/t5526-fetch-submodules.sh \
t/t5529-push-errors.sh t/t5530-upload-pack-error.sh \
t/t5548-push-porcelain.sh \
t/t5552-skipping-fetch-negotiator.sh \
t/t5572-pull-submodule.sh t/t5608-clone-2gb.sh \
t/t5614-clone-submodules-shallow.sh \
t/t7508-status.sh t/t7606-merge-custom.sh \
t/t9302-fast-import-unpack-limit.sh
We excluded one set of test scripts in these commands, though: the range
of `git p4` tests. The reason? `git p4` stores the (foreign) remote
branch in the branch called `p4/master`, which is obviously not the
default branch. Manual analysis revealed that only five of these tests
actually require a specific default branch name to pass; They were
modified thusly:
$ sed -i '/^ *\. \.\/lib-git-p4\.sh$/i\
GIT_TEST_DEFAULT_INITIAL_BRANCH_NAME=master\
export GIT_TEST_DEFAULT_INITIAL_BRANCH_NAME\
' t/t980[0167]*.sh t/t9811*.sh
Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2020-11-18 23:44:19 +00:00
|
|
|
export GIT_TEST_DEFAULT_INITIAL_BRANCH_NAME
|
|
|
|
|
2012-11-28 22:11:01 +00:00
|
|
|
. ./test-lib.sh
|
2013-04-14 10:57:07 +00:00
|
|
|
. "$TEST_DIRECTORY"/lib-gpg.sh
|
2012-11-28 22:11:01 +00:00
|
|
|
|
2019-04-12 12:00:31 +00:00
|
|
|
PATH="$TEST_DIRECTORY/t5801:$PATH"
|
|
|
|
|
2012-11-28 22:11:01 +00:00
|
|
|
compare_refs() {
|
2020-03-26 08:27:55 +00:00
|
|
|
fail= &&
|
|
|
|
if test "x$1" = 'x!'
|
|
|
|
then
|
|
|
|
fail='!' &&
|
|
|
|
shift
|
|
|
|
fi &&
|
2012-11-28 22:11:01 +00:00
|
|
|
git --git-dir="$1/.git" rev-parse --verify $2 >expect &&
|
|
|
|
git --git-dir="$3/.git" rev-parse --verify $4 >actual &&
|
2020-03-26 08:27:55 +00:00
|
|
|
eval $fail test_cmp expect actual
|
2012-11-28 22:11:01 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
test_expect_success 'setup repository' '
|
2012-11-28 22:11:04 +00:00
|
|
|
git init server &&
|
|
|
|
(cd server &&
|
2012-11-28 22:11:01 +00:00
|
|
|
echo content >file &&
|
|
|
|
git add file &&
|
2012-11-28 22:11:04 +00:00
|
|
|
git commit -m one)
|
2012-11-28 22:11:01 +00:00
|
|
|
'
|
|
|
|
|
|
|
|
test_expect_success 'cloning from local repo' '
|
2012-11-28 22:11:04 +00:00
|
|
|
git clone "testgit::${PWD}/server" local &&
|
|
|
|
test_cmp server/file local/file
|
2012-11-28 22:11:01 +00:00
|
|
|
'
|
|
|
|
|
|
|
|
test_expect_success 'create new commit on remote' '
|
2012-11-28 22:11:04 +00:00
|
|
|
(cd server &&
|
2012-11-28 22:11:01 +00:00
|
|
|
echo content >>file &&
|
2012-11-28 22:11:04 +00:00
|
|
|
git commit -a -m two)
|
2012-11-28 22:11:01 +00:00
|
|
|
'
|
|
|
|
|
|
|
|
test_expect_success 'pulling from local repo' '
|
2012-11-28 22:11:04 +00:00
|
|
|
(cd local && git pull) &&
|
|
|
|
test_cmp server/file local/file
|
2012-11-28 22:11:01 +00:00
|
|
|
'
|
|
|
|
|
|
|
|
test_expect_success 'pushing to local repo' '
|
2012-11-28 22:11:04 +00:00
|
|
|
(cd local &&
|
2012-11-28 22:11:01 +00:00
|
|
|
echo content >>file &&
|
|
|
|
git commit -a -m three &&
|
|
|
|
git push) &&
|
2012-11-28 22:11:04 +00:00
|
|
|
compare_refs local HEAD server HEAD
|
2012-11-28 22:11:01 +00:00
|
|
|
'
|
|
|
|
|
|
|
|
test_expect_success 'fetch new branch' '
|
2012-11-28 22:11:04 +00:00
|
|
|
(cd server &&
|
|
|
|
git reset --hard &&
|
2012-11-28 22:11:01 +00:00
|
|
|
git checkout -b new &&
|
|
|
|
echo content >>file &&
|
2012-11-28 22:11:04 +00:00
|
|
|
git commit -a -m five
|
2012-11-28 22:11:01 +00:00
|
|
|
) &&
|
2012-11-28 22:11:04 +00:00
|
|
|
(cd local &&
|
2012-11-28 22:11:01 +00:00
|
|
|
git fetch origin new
|
|
|
|
) &&
|
2012-11-28 22:11:04 +00:00
|
|
|
compare_refs server HEAD local FETCH_HEAD
|
2012-11-28 22:11:01 +00:00
|
|
|
'
|
|
|
|
|
|
|
|
test_expect_success 'fetch multiple branches' '
|
2012-11-28 22:11:04 +00:00
|
|
|
(cd local &&
|
2012-11-28 22:11:01 +00:00
|
|
|
git fetch
|
|
|
|
) &&
|
2020-11-18 23:44:35 +00:00
|
|
|
compare_refs server main local refs/remotes/origin/main &&
|
2012-11-28 22:11:04 +00:00
|
|
|
compare_refs server new local refs/remotes/origin/new
|
2012-11-28 22:11:01 +00:00
|
|
|
'
|
|
|
|
|
|
|
|
test_expect_success 'push when remote has extra refs' '
|
2012-11-28 22:11:04 +00:00
|
|
|
(cd local &&
|
2020-11-18 23:44:35 +00:00
|
|
|
git reset --hard origin/main &&
|
2012-11-28 22:11:01 +00:00
|
|
|
echo content >>file &&
|
|
|
|
git commit -a -m six &&
|
|
|
|
git push
|
|
|
|
) &&
|
2020-11-18 23:44:35 +00:00
|
|
|
compare_refs local main server main
|
2012-11-28 22:11:01 +00:00
|
|
|
'
|
|
|
|
|
|
|
|
test_expect_success 'push new branch by name' '
|
2012-11-28 22:11:04 +00:00
|
|
|
(cd local &&
|
2012-11-28 22:11:01 +00:00
|
|
|
git checkout -b new-name &&
|
|
|
|
echo content >>file &&
|
|
|
|
git commit -a -m seven &&
|
|
|
|
git push origin new-name
|
|
|
|
) &&
|
2012-11-28 22:11:04 +00:00
|
|
|
compare_refs local HEAD server refs/heads/new-name
|
2012-11-28 22:11:01 +00:00
|
|
|
'
|
|
|
|
|
2014-04-20 18:59:25 +00:00
|
|
|
test_expect_success 'push new branch with old:new refspec' '
|
2012-11-28 22:11:04 +00:00
|
|
|
(cd local &&
|
2012-11-28 22:11:01 +00:00
|
|
|
git push origin new-name:new-refspec
|
|
|
|
) &&
|
2012-11-28 22:11:04 +00:00
|
|
|
compare_refs local HEAD server refs/heads/new-refspec
|
2012-11-28 22:11:01 +00:00
|
|
|
'
|
|
|
|
|
2014-04-20 18:59:26 +00:00
|
|
|
test_expect_success 'push new branch with HEAD:new refspec' '
|
|
|
|
(cd local &&
|
2018-07-02 00:24:01 +00:00
|
|
|
git checkout new-name &&
|
2014-04-20 18:59:26 +00:00
|
|
|
git push origin HEAD:new-refspec-2
|
|
|
|
) &&
|
|
|
|
compare_refs local HEAD server refs/heads/new-refspec-2
|
|
|
|
'
|
|
|
|
|
2014-04-20 18:59:29 +00:00
|
|
|
test_expect_success 'push delete branch' '
|
|
|
|
(cd local &&
|
|
|
|
git push origin :new-name
|
|
|
|
) &&
|
|
|
|
test_must_fail git --git-dir="server/.git" \
|
|
|
|
rev-parse --verify refs/heads/new-name
|
|
|
|
'
|
|
|
|
|
2013-11-12 20:56:56 +00:00
|
|
|
test_expect_success 'forced push' '
|
|
|
|
(cd local &&
|
|
|
|
git checkout -b force-test &&
|
|
|
|
echo content >> file &&
|
|
|
|
git commit -a -m eight &&
|
|
|
|
git push origin force-test &&
|
|
|
|
echo content >> file &&
|
|
|
|
git commit -a --amend -m eight-modified &&
|
|
|
|
git push --force origin force-test
|
|
|
|
) &&
|
|
|
|
compare_refs local refs/heads/force-test server refs/heads/force-test
|
|
|
|
'
|
|
|
|
|
2012-11-28 22:11:05 +00:00
|
|
|
test_expect_success 'cloning without refspec' '
|
2019-06-04 02:13:26 +00:00
|
|
|
GIT_REMOTE_TESTGIT_NOREFSPEC=1 \
|
2013-04-18 04:14:31 +00:00
|
|
|
git clone "testgit::${PWD}/server" local2 2>error &&
|
2023-10-31 05:23:30 +00:00
|
|
|
test_grep "this remote helper should implement refspec capability" error &&
|
2012-11-28 22:11:05 +00:00
|
|
|
compare_refs local2 HEAD server HEAD
|
|
|
|
'
|
|
|
|
|
|
|
|
test_expect_success 'pulling without refspecs' '
|
|
|
|
(cd local2 &&
|
|
|
|
git reset --hard &&
|
2019-06-04 02:13:26 +00:00
|
|
|
GIT_REMOTE_TESTGIT_NOREFSPEC=1 git pull 2>../error) &&
|
2023-10-31 05:23:30 +00:00
|
|
|
test_grep "this remote helper should implement refspec capability" error &&
|
2012-11-28 22:11:05 +00:00
|
|
|
compare_refs local2 HEAD server HEAD
|
|
|
|
'
|
|
|
|
|
2013-04-18 04:14:30 +00:00
|
|
|
test_expect_success 'pushing without refspecs' '
|
2012-11-28 22:11:05 +00:00
|
|
|
test_when_finished "(cd local2 && git reset --hard origin)" &&
|
|
|
|
(cd local2 &&
|
|
|
|
echo content >>file &&
|
|
|
|
git commit -a -m ten &&
|
2019-06-04 02:13:26 +00:00
|
|
|
GIT_REMOTE_TESTGIT_NOREFSPEC=1 &&
|
|
|
|
export GIT_REMOTE_TESTGIT_NOREFSPEC &&
|
2013-04-25 17:18:37 +00:00
|
|
|
test_must_fail git push 2>../error) &&
|
2023-10-31 05:23:30 +00:00
|
|
|
test_grep "remote-helper doesn.t support push; refspec needed" error
|
2012-11-28 22:11:05 +00:00
|
|
|
'
|
|
|
|
|
|
|
|
test_expect_success 'pulling without marks' '
|
|
|
|
(cd local2 &&
|
|
|
|
GIT_REMOTE_TESTGIT_NO_MARKS=1 git pull) &&
|
|
|
|
compare_refs local2 HEAD server HEAD
|
|
|
|
'
|
|
|
|
|
|
|
|
test_expect_failure 'pushing without marks' '
|
|
|
|
test_when_finished "(cd local2 && git reset --hard origin)" &&
|
|
|
|
(cd local2 &&
|
|
|
|
echo content >>file &&
|
|
|
|
git commit -a -m twelve &&
|
|
|
|
GIT_REMOTE_TESTGIT_NO_MARKS=1 git push) &&
|
|
|
|
compare_refs local2 HEAD server HEAD
|
|
|
|
'
|
|
|
|
|
fast-export: don't handle uninteresting refs
They have been marked as UNINTERESTING for a reason, lets respect
that. Currently the first ref is handled properly, but not the
rest. Assuming that all the refs point at the same commit in the
following example:
% git fast-export master ^uninteresting ^foo ^bar
reset refs/heads/bar
from :0
reset refs/heads/foo
from :0
reset refs/heads/uninteresting
from :0
% git fast-export ^uninteresting ^foo ^bar master
reset refs/heads/master
from :0
reset refs/heads/bar
from :0
reset refs/heads/foo
from :0
Clearly this is wrong; the negative refs should be ignored.
After this patch:
% git fast-export ^uninteresting ^foo ^bar master
# nothing
% git fast-export master ^uninteresting ^foo ^bar
# nothing
And even more, it would only happen if the ref is pointing to exactly
the same commit, but not otherwise:
% git fast-export ^next next
reset refs/heads/next
from :0
% git fast-export ^next next^{commit}
# nothing
% git fast-export ^next next~0
# nothing
% git fast-export ^next next~1
# nothing
% git fast-export ^next next~2
# nothing
The reason this happens is that before traversing the commits,
fast-export checks if any of the refs point to the same object, and any
duplicated ref gets added to a list in order to issue 'reset' commands
after the traversing. Unfortunately, it's not even checking if the
commit is flagged as UNINTERESTING. The fix of course, is to check it.
However, in order to do it properly we need to get the UNINTERESTING
flag from the command line, not from the commit object, because
"^foo bar" will mark the commit 'bar' uninteresting if foo and bar
points at the same commit. rev_cmdline_info, which was introduced
exactly to handle this situation, contains all the information we
need for get_tags_and_duplicates(), plus the ref flag. This way the
rest of the positive refs will remain untouched; it's only the
negative ones that change in behavior.
Signed-off-by: Felipe Contreras <felipe.contreras@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2012-11-28 22:23:59 +00:00
|
|
|
test_expect_success 'push all with existing object' '
|
|
|
|
(cd local &&
|
2020-11-18 23:44:35 +00:00
|
|
|
git branch dup2 main &&
|
fast-export: don't handle uninteresting refs
They have been marked as UNINTERESTING for a reason, lets respect
that. Currently the first ref is handled properly, but not the
rest. Assuming that all the refs point at the same commit in the
following example:
% git fast-export master ^uninteresting ^foo ^bar
reset refs/heads/bar
from :0
reset refs/heads/foo
from :0
reset refs/heads/uninteresting
from :0
% git fast-export ^uninteresting ^foo ^bar master
reset refs/heads/master
from :0
reset refs/heads/bar
from :0
reset refs/heads/foo
from :0
Clearly this is wrong; the negative refs should be ignored.
After this patch:
% git fast-export ^uninteresting ^foo ^bar master
# nothing
% git fast-export master ^uninteresting ^foo ^bar
# nothing
And even more, it would only happen if the ref is pointing to exactly
the same commit, but not otherwise:
% git fast-export ^next next
reset refs/heads/next
from :0
% git fast-export ^next next^{commit}
# nothing
% git fast-export ^next next~0
# nothing
% git fast-export ^next next~1
# nothing
% git fast-export ^next next~2
# nothing
The reason this happens is that before traversing the commits,
fast-export checks if any of the refs point to the same object, and any
duplicated ref gets added to a list in order to issue 'reset' commands
after the traversing. Unfortunately, it's not even checking if the
commit is flagged as UNINTERESTING. The fix of course, is to check it.
However, in order to do it properly we need to get the UNINTERESTING
flag from the command line, not from the commit object, because
"^foo bar" will mark the commit 'bar' uninteresting if foo and bar
points at the same commit. rev_cmdline_info, which was introduced
exactly to handle this situation, contains all the information we
need for get_tags_and_duplicates(), plus the ref flag. This way the
rest of the positive refs will remain untouched; it's only the
negative ones that change in behavior.
Signed-off-by: Felipe Contreras <felipe.contreras@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2012-11-28 22:23:59 +00:00
|
|
|
git push origin --all
|
|
|
|
) &&
|
|
|
|
compare_refs local dup2 server dup2
|
|
|
|
'
|
|
|
|
|
fast-export: make sure updated refs get updated
When an object has already been exported (and thus is in the marks) it's
flagged as SHOWN, so it will not be exported again, even if in a later
time it's exported through a different ref.
We don't need the object to be exported again, but we want the ref
updated, which doesn't happen.
Since we can't know if a ref was exported or not, let's just assume that
if the commit was marked (flags & SHOWN), the user still wants the ref
updated.
IOW: If it's specified in the command line, it will get updated,
regardless of whether or not the object was marked.
So:
% git branch test master
% git fast-export $mark_flags master
% git fast-export $mark_flags test
Would export 'test' properly.
Additionally, this fixes issues with remote helpers; now they can push
refs whose objects have already been exported, and a few other issues as
well. Update the tests accordingly.
Signed-off-by: Felipe Contreras <felipe.contreras@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2012-11-28 22:24:00 +00:00
|
|
|
test_expect_success 'push ref with existing object' '
|
|
|
|
(cd local &&
|
2020-11-18 23:44:35 +00:00
|
|
|
git branch dup main &&
|
fast-export: make sure updated refs get updated
When an object has already been exported (and thus is in the marks) it's
flagged as SHOWN, so it will not be exported again, even if in a later
time it's exported through a different ref.
We don't need the object to be exported again, but we want the ref
updated, which doesn't happen.
Since we can't know if a ref was exported or not, let's just assume that
if the commit was marked (flags & SHOWN), the user still wants the ref
updated.
IOW: If it's specified in the command line, it will get updated,
regardless of whether or not the object was marked.
So:
% git branch test master
% git fast-export $mark_flags master
% git fast-export $mark_flags test
Would export 'test' properly.
Additionally, this fixes issues with remote helpers; now they can push
refs whose objects have already been exported, and a few other issues as
well. Update the tests accordingly.
Signed-off-by: Felipe Contreras <felipe.contreras@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2012-11-28 22:24:00 +00:00
|
|
|
git push origin dup
|
|
|
|
) &&
|
|
|
|
compare_refs local dup server dup
|
|
|
|
'
|
|
|
|
|
2013-04-14 10:57:07 +00:00
|
|
|
test_expect_success GPG 'push signed tag' '
|
|
|
|
(cd local &&
|
2020-11-18 23:44:35 +00:00
|
|
|
git checkout main &&
|
2013-04-14 10:57:07 +00:00
|
|
|
git tag -s -m signed-tag signed-tag &&
|
|
|
|
git push origin signed-tag
|
|
|
|
) &&
|
2013-04-14 10:57:08 +00:00
|
|
|
compare_refs local signed-tag^{} server signed-tag^{} &&
|
2020-03-26 08:27:55 +00:00
|
|
|
compare_refs ! local signed-tag server signed-tag
|
2013-04-14 10:57:08 +00:00
|
|
|
'
|
|
|
|
|
|
|
|
test_expect_success GPG 'push signed tag with signed-tags capability' '
|
|
|
|
(cd local &&
|
2020-11-18 23:44:35 +00:00
|
|
|
git checkout main &&
|
2013-04-14 10:57:08 +00:00
|
|
|
git tag -s -m signed-tag signed-tag-2 &&
|
|
|
|
GIT_REMOTE_TESTGIT_SIGNED_TAGS=1 git push origin signed-tag-2
|
|
|
|
) &&
|
|
|
|
compare_refs local signed-tag-2 server signed-tag-2
|
2013-04-14 10:57:07 +00:00
|
|
|
'
|
|
|
|
|
2013-04-18 04:14:33 +00:00
|
|
|
test_expect_success 'push update refs' '
|
|
|
|
(cd local &&
|
2020-11-18 23:44:35 +00:00
|
|
|
git checkout -b update main &&
|
2013-04-18 04:14:33 +00:00
|
|
|
echo update >>file &&
|
|
|
|
git commit -a -m update &&
|
2013-05-10 12:08:29 +00:00
|
|
|
git push origin update &&
|
2013-04-18 04:14:33 +00:00
|
|
|
git rev-parse --verify remotes/origin/update >expect &&
|
|
|
|
git rev-parse --verify testgit/origin/heads/update >actual &&
|
|
|
|
test_cmp expect actual
|
|
|
|
)
|
|
|
|
'
|
|
|
|
|
2013-09-03 15:45:14 +00:00
|
|
|
test_expect_success 'push update refs disabled by no-private-update' '
|
|
|
|
(cd local &&
|
|
|
|
echo more-update >>file &&
|
|
|
|
git commit -a -m more-update &&
|
|
|
|
git rev-parse --verify testgit/origin/heads/update >expect &&
|
|
|
|
GIT_REMOTE_TESTGIT_NO_PRIVATE_UPDATE=t git push origin update &&
|
|
|
|
git rev-parse --verify testgit/origin/heads/update >actual &&
|
|
|
|
test_cmp expect actual
|
|
|
|
)
|
|
|
|
'
|
|
|
|
|
2013-05-10 12:08:30 +00:00
|
|
|
test_expect_success 'push update refs failure' '
|
|
|
|
(cd local &&
|
|
|
|
git checkout update &&
|
|
|
|
echo "update fail" >>file &&
|
|
|
|
git commit -a -m "update fail" &&
|
|
|
|
git rev-parse --verify testgit/origin/heads/update >expect &&
|
2014-05-20 21:18:11 +00:00
|
|
|
test_expect_code 1 env GIT_REMOTE_TESTGIT_FAILURE="non-fast forward" \
|
|
|
|
git push origin update &&
|
2013-05-10 12:08:30 +00:00
|
|
|
git rev-parse --verify testgit/origin/heads/update >actual &&
|
|
|
|
test_cmp expect actual
|
|
|
|
)
|
|
|
|
'
|
|
|
|
|
2014-05-20 21:18:11 +00:00
|
|
|
clean_mark () {
|
|
|
|
cut -f 2 -d ' ' "$1" |
|
|
|
|
git cat-file --batch-check |
|
|
|
|
grep commit |
|
|
|
|
sort >$(basename "$1")
|
|
|
|
}
|
|
|
|
|
2013-04-10 21:15:52 +00:00
|
|
|
test_expect_success 'proper failure checks for fetching' '
|
2014-05-20 21:18:11 +00:00
|
|
|
(cd local &&
|
|
|
|
test_must_fail env GIT_REMOTE_TESTGIT_FAILURE=1 git fetch 2>error &&
|
2023-10-31 05:23:30 +00:00
|
|
|
test_grep -q "error while running fast-import" error
|
2013-04-10 21:15:52 +00:00
|
|
|
)
|
|
|
|
'
|
|
|
|
|
|
|
|
test_expect_success 'proper failure checks for pushing' '
|
2015-09-05 13:12:46 +00:00
|
|
|
test_when_finished "rm -rf local/git.marks local/testgit.marks" &&
|
2014-03-18 18:54:05 +00:00
|
|
|
(cd local &&
|
2020-11-18 23:44:35 +00:00
|
|
|
git checkout -b crash main &&
|
2014-05-20 21:18:11 +00:00
|
|
|
echo crash >>file &&
|
|
|
|
git commit -a -m crash &&
|
|
|
|
test_must_fail env GIT_REMOTE_TESTGIT_FAILURE=1 git push --all &&
|
2015-09-05 13:12:46 +00:00
|
|
|
clean_mark ".git/testgit/origin/git.marks" &&
|
|
|
|
clean_mark ".git/testgit/origin/testgit.marks" &&
|
|
|
|
test_cmp git.marks testgit.marks
|
2013-04-10 21:15:52 +00:00
|
|
|
)
|
|
|
|
'
|
|
|
|
|
2013-05-03 23:41:59 +00:00
|
|
|
test_expect_success 'push messages' '
|
|
|
|
(cd local &&
|
2020-11-18 23:44:35 +00:00
|
|
|
git checkout -b new_branch main &&
|
2013-05-03 23:41:59 +00:00
|
|
|
echo new >>file &&
|
|
|
|
git commit -a -m new &&
|
|
|
|
git push origin new_branch &&
|
|
|
|
git fetch origin &&
|
|
|
|
echo new >>file &&
|
|
|
|
git commit -a -m new &&
|
|
|
|
git push origin new_branch 2> msg &&
|
|
|
|
! grep "\[new branch\]" msg
|
|
|
|
)
|
|
|
|
'
|
|
|
|
|
transport-helper: do not request symbolic refs to remote helpers
A typical remote helper will return a `list` of refs containing a symbolic
ref HEAD, pointing to, e.g. refs/heads/master. In the case of a clone, all
the refs are being requested through `fetch` or `import`, including the
symbolic ref.
While this works properly, in some cases of a fetch, like `git fetch url`
or `git fetch origin HEAD`, or any fetch command involving a symbolic ref
without also fetching the corresponding ref it points to, the fetch command
fails with:
fatal: bad object 0000000000000000000000000000000000000000
error: <remote> did not send all necessary objects
(in the case the remote helper returned '?' values to the `list` command).
This is because there is only one ref given to fetch(), and it's not
further resolved to something at the end of fetch_with_import().
While this can be somehow handled in the remote helper itself, by adding
a refspec for the symbolic ref, and storing an explicit ref in a private
namespace, and then handling the `import` for that symbolic ref
specifically, very few existing remote helpers are actually doing that.
So, instead of requesting the exact list of wanted refs to remote helpers,
treat symbolic refs differently and request the ref they point to instead.
Then, resolve the symbolic refs values based on the pointed ref.
This assumes there is no more than one level of indirection (a symbolic
ref doesn't point to another symbolic ref).
Signed-off-by: Mike Hommey <mh@glandium.org>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2015-01-19 01:35:07 +00:00
|
|
|
test_expect_success 'fetch HEAD' '
|
|
|
|
(cd server &&
|
2020-11-18 23:44:35 +00:00
|
|
|
git checkout main &&
|
transport-helper: do not request symbolic refs to remote helpers
A typical remote helper will return a `list` of refs containing a symbolic
ref HEAD, pointing to, e.g. refs/heads/master. In the case of a clone, all
the refs are being requested through `fetch` or `import`, including the
symbolic ref.
While this works properly, in some cases of a fetch, like `git fetch url`
or `git fetch origin HEAD`, or any fetch command involving a symbolic ref
without also fetching the corresponding ref it points to, the fetch command
fails with:
fatal: bad object 0000000000000000000000000000000000000000
error: <remote> did not send all necessary objects
(in the case the remote helper returned '?' values to the `list` command).
This is because there is only one ref given to fetch(), and it's not
further resolved to something at the end of fetch_with_import().
While this can be somehow handled in the remote helper itself, by adding
a refspec for the symbolic ref, and storing an explicit ref in a private
namespace, and then handling the `import` for that symbolic ref
specifically, very few existing remote helpers are actually doing that.
So, instead of requesting the exact list of wanted refs to remote helpers,
treat symbolic refs differently and request the ref they point to instead.
Then, resolve the symbolic refs values based on the pointed ref.
This assumes there is no more than one level of indirection (a symbolic
ref doesn't point to another symbolic ref).
Signed-off-by: Mike Hommey <mh@glandium.org>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2015-01-19 01:35:07 +00:00
|
|
|
echo more >>file &&
|
|
|
|
git commit -a -m more
|
|
|
|
) &&
|
|
|
|
(cd local &&
|
|
|
|
git fetch origin HEAD
|
|
|
|
) &&
|
|
|
|
compare_refs server HEAD local FETCH_HEAD
|
|
|
|
'
|
|
|
|
|
|
|
|
test_expect_success 'fetch url' '
|
|
|
|
(cd server &&
|
2020-11-18 23:44:35 +00:00
|
|
|
git checkout main &&
|
transport-helper: do not request symbolic refs to remote helpers
A typical remote helper will return a `list` of refs containing a symbolic
ref HEAD, pointing to, e.g. refs/heads/master. In the case of a clone, all
the refs are being requested through `fetch` or `import`, including the
symbolic ref.
While this works properly, in some cases of a fetch, like `git fetch url`
or `git fetch origin HEAD`, or any fetch command involving a symbolic ref
without also fetching the corresponding ref it points to, the fetch command
fails with:
fatal: bad object 0000000000000000000000000000000000000000
error: <remote> did not send all necessary objects
(in the case the remote helper returned '?' values to the `list` command).
This is because there is only one ref given to fetch(), and it's not
further resolved to something at the end of fetch_with_import().
While this can be somehow handled in the remote helper itself, by adding
a refspec for the symbolic ref, and storing an explicit ref in a private
namespace, and then handling the `import` for that symbolic ref
specifically, very few existing remote helpers are actually doing that.
So, instead of requesting the exact list of wanted refs to remote helpers,
treat symbolic refs differently and request the ref they point to instead.
Then, resolve the symbolic refs values based on the pointed ref.
This assumes there is no more than one level of indirection (a symbolic
ref doesn't point to another symbolic ref).
Signed-off-by: Mike Hommey <mh@glandium.org>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2015-01-19 01:35:07 +00:00
|
|
|
echo more >>file &&
|
|
|
|
git commit -a -m more
|
|
|
|
) &&
|
|
|
|
(cd local &&
|
|
|
|
git fetch "testgit::${PWD}/../server"
|
|
|
|
) &&
|
|
|
|
compare_refs server HEAD local FETCH_HEAD
|
|
|
|
'
|
|
|
|
|
2019-06-04 02:13:30 +00:00
|
|
|
test_expect_success 'fetch tag' '
|
2019-06-04 02:13:27 +00:00
|
|
|
(cd server &&
|
|
|
|
git tag v1.0
|
|
|
|
) &&
|
|
|
|
(cd local &&
|
|
|
|
git fetch
|
|
|
|
) &&
|
|
|
|
compare_refs local v1.0 server v1.0
|
|
|
|
'
|
|
|
|
|
2012-11-28 22:11:01 +00:00
|
|
|
test_done
|