t: be explicit about the branch we're pulling from

When we invoke "git pull", be explicit about where we're pulling from.
Git will set some default values for us, but if we want to support a
branch name that isn't the default, we need to be explicit.
This commit is contained in:
brian m. carlson 2020-06-29 15:55:07 +00:00
parent 57a258c5bb
commit d8d2f1e937
No known key found for this signature in database
GPG Key ID: 2D0C9BC12F82B3A1
5 changed files with 5 additions and 5 deletions

@ -57,7 +57,7 @@ begin_test "batch transfer"
# change to the clone's working directory
cd ../clone
git pull
git pull origin master
[ "a" = "$(cat a.dat)" ]

@ -56,7 +56,7 @@ begin_test "chunked transfer encoding"
# change to the clone's working directory
cd ../clone
git pull 2>&1
git pull origin master 2>&1
[ "a" = "$(cat a.dat)" ]

@ -515,7 +515,7 @@ begin_test "fetch with no origin remote"
cd ../no-remote-clone
# pull commits & lfs
git pull 2>&1
git pull origin master 2>&1
assert_local_object "$contents_oid" 1
# now checkout detached HEAD so we're not tracking anything on remote

@ -56,7 +56,7 @@ begin_test "happy path"
# change to the clone's working directory
cd ../clone
git pull
git pull origin master
[ "a" = "$(cat a.dat)" ]

@ -84,7 +84,7 @@ begin_test "fetch from clone reference"
delete_server_object "$reponame" "$oid"
cd "$repo_dir"
GIT_LFS_SKIP_SMUDGE=1 git pull
GIT_LFS_SKIP_SMUDGE=1 git pull origin master
git lfs pull
assert_pointer "master" "a.dat" "$oid" 1