2020-05-24 07:22:51 +00:00
|
|
|
#!/bin/sh
|
|
|
|
|
|
|
|
test_description='tests for git branch --track'
|
|
|
|
|
2020-11-18 23:44:22 +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
|
|
|
|
|
2023-06-17 06:41:54 +00:00
|
|
|
TEST_PASSES_SANITIZE_LEAK=true
|
2020-05-24 07:22:51 +00:00
|
|
|
. ./test-lib.sh
|
|
|
|
|
|
|
|
test_expect_success 'setup' '
|
|
|
|
test_commit one &&
|
|
|
|
test_commit two
|
|
|
|
'
|
|
|
|
|
|
|
|
test_expect_success 'checkout --track -b creates a new tracking branch' '
|
2020-11-18 23:44:22 +00:00
|
|
|
git checkout --track -b branch1 main &&
|
2020-05-24 07:22:51 +00:00
|
|
|
test $(git rev-parse --abbrev-ref HEAD) = branch1 &&
|
|
|
|
test $(git config --get branch.branch1.remote) = . &&
|
2020-11-18 23:44:22 +00:00
|
|
|
test $(git config --get branch.branch1.merge) = refs/heads/main
|
2020-05-24 07:22:51 +00:00
|
|
|
'
|
|
|
|
|
2020-05-24 07:23:00 +00:00
|
|
|
test_expect_success 'checkout --track -b rejects an extra path argument' '
|
2020-11-18 23:44:22 +00:00
|
|
|
test_must_fail git checkout --track -b branch2 main one.t 2>err &&
|
2023-10-31 05:23:30 +00:00
|
|
|
test_grep "cannot be used with updating paths" err
|
2020-05-24 07:22:51 +00:00
|
|
|
'
|
|
|
|
|
branch: add flags and config to inherit tracking
It can be helpful when creating a new branch to use the existing
tracking configuration from the branch point. However, there is
currently not a method to automatically do so.
Teach git-{branch,checkout,switch} an "inherit" argument to the
"--track" option. When this is set, creating a new branch will cause the
tracking configuration to default to the configuration of the branch
point, if set.
For example, if branch "main" tracks "origin/main", and we run
`git checkout --track=inherit -b feature main`, then branch "feature"
will track "origin/main". Thus, `git status` will show us how far
ahead/behind we are from origin, and `git pull` will pull from origin.
This is particularly useful when creating branches across many
submodules, such as with `git submodule foreach ...` (or if running with
a patch such as [1], which we use at $job), as it avoids having to
manually set tracking info for each submodule.
Since we've added an argument to "--track", also add "--track=direct" as
another way to explicitly get the original "--track" behavior ("--track"
without an argument still works as well).
Finally, teach branch.autoSetupMerge a new "inherit" option. When this
is set, "--track=inherit" becomes the default behavior.
[1]: https://lore.kernel.org/git/20180927221603.148025-1-sbeller@google.com/
Signed-off-by: Josh Steadmon <steadmon@google.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2021-12-21 03:30:23 +00:00
|
|
|
test_expect_success 'checkout --track -b overrides autoSetupMerge=inherit' '
|
|
|
|
# Set up tracking config on main
|
|
|
|
test_config branch.main.remote origin &&
|
|
|
|
test_config branch.main.merge refs/heads/some-branch &&
|
|
|
|
test_config branch.autoSetupMerge inherit &&
|
|
|
|
# With --track=inherit, we copy the tracking config from main
|
|
|
|
git checkout --track=inherit -b b1 main &&
|
|
|
|
test_cmp_config origin branch.b1.remote &&
|
|
|
|
test_cmp_config refs/heads/some-branch branch.b1.merge &&
|
|
|
|
# With branch.autoSetupMerge=inherit, we do the same
|
|
|
|
git checkout -b b2 main &&
|
|
|
|
test_cmp_config origin branch.b2.remote &&
|
|
|
|
test_cmp_config refs/heads/some-branch branch.b2.merge &&
|
|
|
|
# But --track overrides this
|
|
|
|
git checkout --track -b b3 main &&
|
|
|
|
test_cmp_config . branch.b3.remote &&
|
|
|
|
test_cmp_config refs/heads/main branch.b3.merge &&
|
|
|
|
# And --track=direct does as well
|
|
|
|
git checkout --track=direct -b b4 main &&
|
|
|
|
test_cmp_config . branch.b4.remote &&
|
|
|
|
test_cmp_config refs/heads/main branch.b4.merge
|
|
|
|
'
|
|
|
|
|
2020-05-24 07:22:51 +00:00
|
|
|
test_done
|