git-lfs/t/t-clone-deprecated.sh
Chris Darroch ed3decf753 use backticks around commands in messages
A number of message strings contain embedded Git or Git LFS
commands, and while in many cases these are already delimited
with backticks, in other cases they are not.

We therefore rework the formatting of these messages to accord
with the general practice of using backticks to delimit "git"
and "git lfs" commands.

In one case for the "git lfs clone" command this requires us
to split a multi-line message into several parts, but that
also has the advantage that we can move some of the fixed
formatting and newlines out of the translatable message strings.

Note that some of these messages are not yet passed as translation
strings, but we will address that issue in a subsequent commit.
2022-01-29 22:35:10 -08:00

22 lines
568 B
Bash
Executable File

#!/usr/bin/env bash
. "$(dirname "$0")/testlib.sh"
ensure_git_version_isnt $VERSION_LOWER "2.15.0"
begin_test "clone (deprecated on new versions of Git)"
(
set -e
reponame="clone-deprecated-recent-versions"
setup_remote_repo "$reponame"
mkdir -p "$reponame"
pushd "$reponame" > /dev/null
git lfs clone "$GITSERVER/$reponame" 2>&1 | tee clone.log
grep "WARNING: \`git lfs clone\` is deprecated and will not be updated" clone.log
grep "\`git clone\` has been updated in upstream Git to have comparable" clone.log
popd > /dev/null
)
end_test