2015-07-30 02:37:31 +00:00
#!/usr/bin/env bash
2015-05-26 21:49:04 +00:00
2018-07-10 18:48:02 +00:00
. " $( dirname " $0 " ) /testlib.sh "
2015-05-26 21:49:04 +00:00
2015-05-26 22:08:03 +00:00
begin_test "update"
2015-05-26 21:49:04 +00:00
(
set -e
pre_push_hook = " #!/bin/sh
hooks: mention core.hookspath instead of just .git/hooks
In some cases, users may use `core.hooksPath` to locate their hooks in a
different location. However, right now, our hook and installation
instructions mention only `.git/hooks`.
We can update the instructions without a problem, but we don't want to
hard-code the hook path into the hooks themselves because of things like
symlinks and moved repository, plus the fact that we can't update a hook
automatically unless it's identical minus some whitespace changes. To
avoid spuriously failing to update a hook, let's print the right
location with the instructions, and just mention `core.hookspath` and
`.git/hooks` in the message, leaving it to the user to discover.
Note that technically, core.hookspath was not implemented until Git
2.9.0. However, while we still support older versions of Git, no
presently supported version of Ubuntu or Debian offers a version older
than 2.11, so the risk of practical confusion by mentioning this is low.
Nevertheless, make our tests pass by checking for an old Git explicitly.
2023-01-04 19:48:38 +00:00
command -v git-lfs >/dev/null 2>& 1 || { echo >& 2 \" \\ nThis repository is configured for Git LFS but 'git-lfs' was not found on your path. If you no longer wish to use Git LFS, remove this hook by deleting the 'pre-push' file in the hooks directory ( set by 'core.hookspath' ; usually '.git/hooks' ) .\\ n\" ; exit 2; }
2015-05-26 21:49:04 +00:00
git lfs pre-push \" \$ @\" "
2017-01-02 13:07:53 +00:00
post_checkout_hook = " #!/bin/sh
hooks: mention core.hookspath instead of just .git/hooks
In some cases, users may use `core.hooksPath` to locate their hooks in a
different location. However, right now, our hook and installation
instructions mention only `.git/hooks`.
We can update the instructions without a problem, but we don't want to
hard-code the hook path into the hooks themselves because of things like
symlinks and moved repository, plus the fact that we can't update a hook
automatically unless it's identical minus some whitespace changes. To
avoid spuriously failing to update a hook, let's print the right
location with the instructions, and just mention `core.hookspath` and
`.git/hooks` in the message, leaving it to the user to discover.
Note that technically, core.hookspath was not implemented until Git
2.9.0. However, while we still support older versions of Git, no
presently supported version of Ubuntu or Debian offers a version older
than 2.11, so the risk of practical confusion by mentioning this is low.
Nevertheless, make our tests pass by checking for an old Git explicitly.
2023-01-04 19:48:38 +00:00
command -v git-lfs >/dev/null 2>& 1 || { echo >& 2 \" \\ nThis repository is configured for Git LFS but 'git-lfs' was not found on your path. If you no longer wish to use Git LFS, remove this hook by deleting the 'post-checkout' file in the hooks directory ( set by 'core.hookspath' ; usually '.git/hooks' ) .\\ n\" ; exit 2; }
2017-01-02 13:07:53 +00:00
git lfs post-checkout \" \$ @\" "
2017-01-02 14:36:28 +00:00
post_commit_hook = " #!/bin/sh
hooks: mention core.hookspath instead of just .git/hooks
In some cases, users may use `core.hooksPath` to locate their hooks in a
different location. However, right now, our hook and installation
instructions mention only `.git/hooks`.
We can update the instructions without a problem, but we don't want to
hard-code the hook path into the hooks themselves because of things like
symlinks and moved repository, plus the fact that we can't update a hook
automatically unless it's identical minus some whitespace changes. To
avoid spuriously failing to update a hook, let's print the right
location with the instructions, and just mention `core.hookspath` and
`.git/hooks` in the message, leaving it to the user to discover.
Note that technically, core.hookspath was not implemented until Git
2.9.0. However, while we still support older versions of Git, no
presently supported version of Ubuntu or Debian offers a version older
than 2.11, so the risk of practical confusion by mentioning this is low.
Nevertheless, make our tests pass by checking for an old Git explicitly.
2023-01-04 19:48:38 +00:00
command -v git-lfs >/dev/null 2>& 1 || { echo >& 2 \" \\ nThis repository is configured for Git LFS but 'git-lfs' was not found on your path. If you no longer wish to use Git LFS, remove this hook by deleting the 'post-commit' file in the hooks directory ( set by 'core.hookspath' ; usually '.git/hooks' ) .\\ n\" ; exit 2; }
2017-01-02 14:36:28 +00:00
git lfs post-commit \" \$ @\" "
2017-01-02 16:56:47 +00:00
post_merge_hook = " #!/bin/sh
hooks: mention core.hookspath instead of just .git/hooks
In some cases, users may use `core.hooksPath` to locate their hooks in a
different location. However, right now, our hook and installation
instructions mention only `.git/hooks`.
We can update the instructions without a problem, but we don't want to
hard-code the hook path into the hooks themselves because of things like
symlinks and moved repository, plus the fact that we can't update a hook
automatically unless it's identical minus some whitespace changes. To
avoid spuriously failing to update a hook, let's print the right
location with the instructions, and just mention `core.hookspath` and
`.git/hooks` in the message, leaving it to the user to discover.
Note that technically, core.hookspath was not implemented until Git
2.9.0. However, while we still support older versions of Git, no
presently supported version of Ubuntu or Debian offers a version older
than 2.11, so the risk of practical confusion by mentioning this is low.
Nevertheless, make our tests pass by checking for an old Git explicitly.
2023-01-04 19:48:38 +00:00
command -v git-lfs >/dev/null 2>& 1 || { echo >& 2 \" \\ nThis repository is configured for Git LFS but 'git-lfs' was not found on your path. If you no longer wish to use Git LFS, remove this hook by deleting the 'post-merge' file in the hooks directory ( set by 'core.hookspath' ; usually '.git/hooks' ) .\\ n\" ; exit 2; }
2017-01-02 16:56:47 +00:00
git lfs post-merge \" \$ @\" "
2015-05-26 21:49:04 +00:00
mkdir without-pre-push
cd without-pre-push
git init
2022-01-29 00:44:16 +00:00
[ "Updated Git hooks." = " $( git lfs update) " ]
2015-05-26 22:15:52 +00:00
[ " $pre_push_hook " = " $( cat .git/hooks/pre-push) " ]
2017-01-02 13:07:53 +00:00
[ " $post_checkout_hook " = " $( cat .git/hooks/post-checkout) " ]
2017-01-02 14:36:28 +00:00
[ " $post_commit_hook " = " $( cat .git/hooks/post-commit) " ]
2017-01-02 16:56:47 +00:00
[ " $post_merge_hook " = " $( cat .git/hooks/post-merge) " ]
2015-05-26 21:49:04 +00:00
# run it again
2022-01-29 00:44:16 +00:00
[ "Updated Git hooks." = " $( git lfs update) " ]
2015-05-26 22:15:52 +00:00
[ " $pre_push_hook " = " $( cat .git/hooks/pre-push) " ]
2017-01-02 13:07:53 +00:00
[ " $post_checkout_hook " = " $( cat .git/hooks/post-checkout) " ]
2017-01-02 14:36:28 +00:00
[ " $post_commit_hook " = " $( cat .git/hooks/post-commit) " ]
2017-01-02 16:56:47 +00:00
[ " $post_merge_hook " = " $( cat .git/hooks/post-merge) " ]
2015-05-26 21:49:04 +00:00
# replace old hook 1
echo " #!/bin/sh
git lfs push --stdin \$ *" > .git/hooks/pre-push
2022-01-29 00:44:16 +00:00
[ "Updated Git hooks." = " $( git lfs update) " ]
2015-05-26 22:15:52 +00:00
[ " $pre_push_hook " = " $( cat .git/hooks/pre-push) " ]
2015-05-26 21:49:04 +00:00
# replace old hook 2
echo " #!/bin/sh
git lfs push --stdin \" \$ @\" " > .git/hooks/pre-push
2022-01-29 00:44:16 +00:00
[ "Updated Git hooks." = " $( git lfs update) " ]
2015-05-26 22:15:52 +00:00
[ " $pre_push_hook " = " $( cat .git/hooks/pre-push) " ]
2015-05-26 21:49:04 +00:00
2015-05-27 21:40:16 +00:00
# replace old hook 3
echo " #!/bin/sh
git lfs pre-push \" \$ @\" " > .git/hooks/pre-push
2022-01-29 00:44:16 +00:00
[ "Updated Git hooks." = " $( git lfs update) " ]
2015-08-13 23:12:17 +00:00
[ " $pre_push_hook " = " $( cat .git/hooks/pre-push) " ]
2016-04-25 13:52:45 +00:00
# replace blank hook
rm .git/hooks/pre-push
touch .git/hooks/pre-push
2017-01-02 13:07:53 +00:00
touch .git/hooks/post-checkout
2017-01-02 16:56:47 +00:00
touch .git/hooks/post-merge
2022-01-29 00:44:16 +00:00
[ "Updated Git hooks." = " $( git lfs update) " ]
2016-04-25 13:52:45 +00:00
[ " $pre_push_hook " = " $( cat .git/hooks/pre-push) " ]
2017-01-02 13:07:53 +00:00
[ " $post_checkout_hook " = " $( cat .git/hooks/post-checkout) " ]
2017-01-02 14:36:28 +00:00
[ " $post_commit_hook " = " $( cat .git/hooks/post-commit) " ]
2017-01-02 16:56:47 +00:00
[ " $post_merge_hook " = " $( cat .git/hooks/post-merge) " ]
2016-04-25 13:52:45 +00:00
2015-08-13 23:12:17 +00:00
# replace old hook 4
echo " #!/bin/sh
command -v git-lfs >/dev/null 2>& 1 || { echo >& 2 \" \\ nThis repository has been set up with Git LFS but Git LFS is not installed.\\ n\" ; exit 0; }
2023-01-04 18:41:55 +00:00
git lfs pre-push \" \$ @\" " > .git/hooks/pre-push
2022-01-29 00:44:16 +00:00
[ "Updated Git hooks." = " $( git lfs update) " ]
2015-08-13 23:12:17 +00:00
[ " $pre_push_hook " = " $( cat .git/hooks/pre-push) " ]
# replace old hook 5
echo " #!/bin/sh
command -v git-lfs >/dev/null 2>& 1 || { echo >& 2 \" \\ nThis repository has been set up with Git LFS but Git LFS is not installed.\\ n\" ; exit 2; }
2023-01-04 18:41:55 +00:00
git lfs pre-push \" \$ @\" " > .git/hooks/pre-push
2022-01-29 00:44:16 +00:00
[ "Updated Git hooks." = " $( git lfs update) " ]
hooks: mention core.hookspath instead of just .git/hooks
In some cases, users may use `core.hooksPath` to locate their hooks in a
different location. However, right now, our hook and installation
instructions mention only `.git/hooks`.
We can update the instructions without a problem, but we don't want to
hard-code the hook path into the hooks themselves because of things like
symlinks and moved repository, plus the fact that we can't update a hook
automatically unless it's identical minus some whitespace changes. To
avoid spuriously failing to update a hook, let's print the right
location with the instructions, and just mention `core.hookspath` and
`.git/hooks` in the message, leaving it to the user to discover.
Note that technically, core.hookspath was not implemented until Git
2.9.0. However, while we still support older versions of Git, no
presently supported version of Ubuntu or Debian offers a version older
than 2.11, so the risk of practical confusion by mentioning this is low.
Nevertheless, make our tests pass by checking for an old Git explicitly.
2023-01-04 19:48:38 +00:00
# replace old hook 6
echo " #!/bin/sh
command -v git-lfs >/dev/null 2>& 1 || { echo >& 2 \" \\ nThis repository is configured for Git LFS but 'git-lfs' was not found on your path. If you no longer wish to use Git LFS, remove this hook by deleting '.git/hooks/pre-push' .\\ n\" ; exit 2; }
git lfs pre-push \" \$ @\" " > .git/hooks/pre-push
[ "Updated Git hooks." = " $( git lfs update) " ]
[ " $pre_push_hook " = " $( cat .git/hooks/pre-push) " ]
2015-05-27 21:40:16 +00:00
[ " $pre_push_hook " = " $( cat .git/hooks/pre-push) " ]
2015-05-26 21:49:04 +00:00
# don't replace unexpected hook
echo "test" > .git/hooks/pre-push
2017-01-02 13:07:53 +00:00
echo "test" > .git/hooks/post-checkout
2017-01-02 14:36:28 +00:00
echo "test" > .git/hooks/post-commit
2017-01-02 16:56:47 +00:00
echo "test" > .git/hooks/post-merge
2015-05-26 21:49:04 +00:00
expected = " Hook already exists: pre-push
2017-07-06 17:43:48 +00:00
test
2015-05-26 21:49:04 +00:00
2016-04-26 11:04:55 +00:00
To resolve this, either:
1: run \` git lfs update --manual\` for instructions on how to merge hooks.
2: run \` git lfs update --force\` to overwrite your hook."
2015-05-26 21:49:04 +00:00
2015-05-26 22:15:52 +00:00
[ " $expected " = " $( git lfs update 2>& 1) " ]
[ "test" = " $( cat .git/hooks/pre-push) " ]
2017-01-02 13:07:53 +00:00
[ "test" = " $( cat .git/hooks/post-checkout) " ]
2017-01-02 14:36:28 +00:00
[ "test" = " $( cat .git/hooks/post-commit) " ]
2017-01-02 16:56:47 +00:00
[ "test" = " $( cat .git/hooks/post-merge) " ]
2015-05-26 21:49:04 +00:00
2016-04-25 09:56:38 +00:00
# Make sure returns non-zero
set +e
git lfs update
if [ $? -eq 0 ]
then
exit 1
fi
set -e
2016-04-26 11:04:55 +00:00
# test manual steps
2022-01-27 07:40:54 +00:00
expected = " Add the following to '.git/hooks/pre-push':
2017-07-11 22:10:30 +00:00
2017-07-06 17:44:07 +00:00
#!/bin/sh
hooks: mention core.hookspath instead of just .git/hooks
In some cases, users may use `core.hooksPath` to locate their hooks in a
different location. However, right now, our hook and installation
instructions mention only `.git/hooks`.
We can update the instructions without a problem, but we don't want to
hard-code the hook path into the hooks themselves because of things like
symlinks and moved repository, plus the fact that we can't update a hook
automatically unless it's identical minus some whitespace changes. To
avoid spuriously failing to update a hook, let's print the right
location with the instructions, and just mention `core.hookspath` and
`.git/hooks` in the message, leaving it to the user to discover.
Note that technically, core.hookspath was not implemented until Git
2.9.0. However, while we still support older versions of Git, no
presently supported version of Ubuntu or Debian offers a version older
than 2.11, so the risk of practical confusion by mentioning this is low.
Nevertheless, make our tests pass by checking for an old Git explicitly.
2023-01-04 19:48:38 +00:00
command -v git-lfs >/dev/null 2>& 1 || { echo >& 2 \" \n This repository is configured for Git LFS but 'git-lfs' was not found on your path. If you no longer wish to use Git LFS, remove this hook by deleting the 'pre-push' file in the hooks directory ( set by 'core.hookspath' ; usually '.git/hooks' ) .\n \" ; exit 2; }
2017-07-06 17:44:07 +00:00
git lfs pre-push \" \$ @\"
2017-01-02 13:07:53 +00:00
2022-01-27 07:40:54 +00:00
Add the following to '.git/hooks/post-checkout' :
2017-07-11 22:10:30 +00:00
2017-07-06 17:44:07 +00:00
#!/bin/sh
hooks: mention core.hookspath instead of just .git/hooks
In some cases, users may use `core.hooksPath` to locate their hooks in a
different location. However, right now, our hook and installation
instructions mention only `.git/hooks`.
We can update the instructions without a problem, but we don't want to
hard-code the hook path into the hooks themselves because of things like
symlinks and moved repository, plus the fact that we can't update a hook
automatically unless it's identical minus some whitespace changes. To
avoid spuriously failing to update a hook, let's print the right
location with the instructions, and just mention `core.hookspath` and
`.git/hooks` in the message, leaving it to the user to discover.
Note that technically, core.hookspath was not implemented until Git
2.9.0. However, while we still support older versions of Git, no
presently supported version of Ubuntu or Debian offers a version older
than 2.11, so the risk of practical confusion by mentioning this is low.
Nevertheless, make our tests pass by checking for an old Git explicitly.
2023-01-04 19:48:38 +00:00
command -v git-lfs >/dev/null 2>& 1 || { echo >& 2 \" \n This repository is configured for Git LFS but 'git-lfs' was not found on your path. If you no longer wish to use Git LFS, remove this hook by deleting the 'post-checkout' file in the hooks directory ( set by 'core.hookspath' ; usually '.git/hooks' ) .\n \" ; exit 2; }
2017-07-06 17:44:07 +00:00
git lfs post-checkout \" \$ @\"
2017-01-02 14:36:28 +00:00
2022-01-27 07:40:54 +00:00
Add the following to '.git/hooks/post-commit' :
2017-07-11 22:10:30 +00:00
2017-07-06 17:44:07 +00:00
#!/bin/sh
hooks: mention core.hookspath instead of just .git/hooks
In some cases, users may use `core.hooksPath` to locate their hooks in a
different location. However, right now, our hook and installation
instructions mention only `.git/hooks`.
We can update the instructions without a problem, but we don't want to
hard-code the hook path into the hooks themselves because of things like
symlinks and moved repository, plus the fact that we can't update a hook
automatically unless it's identical minus some whitespace changes. To
avoid spuriously failing to update a hook, let's print the right
location with the instructions, and just mention `core.hookspath` and
`.git/hooks` in the message, leaving it to the user to discover.
Note that technically, core.hookspath was not implemented until Git
2.9.0. However, while we still support older versions of Git, no
presently supported version of Ubuntu or Debian offers a version older
than 2.11, so the risk of practical confusion by mentioning this is low.
Nevertheless, make our tests pass by checking for an old Git explicitly.
2023-01-04 19:48:38 +00:00
command -v git-lfs >/dev/null 2>& 1 || { echo >& 2 \" \n This repository is configured for Git LFS but 'git-lfs' was not found on your path. If you no longer wish to use Git LFS, remove this hook by deleting the 'post-commit' file in the hooks directory ( set by 'core.hookspath' ; usually '.git/hooks' ) .\n \" ; exit 2; }
2017-07-06 17:44:07 +00:00
git lfs post-commit \" \$ @\"
2017-01-02 16:56:47 +00:00
2022-01-27 07:40:54 +00:00
Add the following to '.git/hooks/post-merge' :
2017-07-11 22:10:30 +00:00
2017-07-06 17:44:07 +00:00
#!/bin/sh
hooks: mention core.hookspath instead of just .git/hooks
In some cases, users may use `core.hooksPath` to locate their hooks in a
different location. However, right now, our hook and installation
instructions mention only `.git/hooks`.
We can update the instructions without a problem, but we don't want to
hard-code the hook path into the hooks themselves because of things like
symlinks and moved repository, plus the fact that we can't update a hook
automatically unless it's identical minus some whitespace changes. To
avoid spuriously failing to update a hook, let's print the right
location with the instructions, and just mention `core.hookspath` and
`.git/hooks` in the message, leaving it to the user to discover.
Note that technically, core.hookspath was not implemented until Git
2.9.0. However, while we still support older versions of Git, no
presently supported version of Ubuntu or Debian offers a version older
than 2.11, so the risk of practical confusion by mentioning this is low.
Nevertheless, make our tests pass by checking for an old Git explicitly.
2023-01-04 19:48:38 +00:00
command -v git-lfs >/dev/null 2>& 1 || { echo >& 2 \" \n This repository is configured for Git LFS but 'git-lfs' was not found on your path. If you no longer wish to use Git LFS, remove this hook by deleting the 'post-merge' file in the hooks directory ( set by 'core.hookspath' ; usually '.git/hooks' ) .\n \" ; exit 2; }
2017-07-06 17:44:07 +00:00
git lfs post-merge \" \$ @\" "
2016-04-26 11:04:55 +00:00
[ " $expected " = " $( git lfs update --manual 2>& 1) " ]
[ "test" = " $( cat .git/hooks/pre-push) " ]
2017-01-02 13:07:53 +00:00
[ "test" = " $( cat .git/hooks/post-checkout) " ]
2017-01-02 14:36:28 +00:00
[ "test" = " $( cat .git/hooks/post-commit) " ]
2017-01-02 16:56:47 +00:00
[ "test" = " $( cat .git/hooks/post-merge) " ]
2016-04-26 11:04:55 +00:00
2015-05-26 21:49:04 +00:00
# force replace unexpected hook
2022-01-29 00:44:16 +00:00
[ "Updated Git hooks." = " $( git lfs update --force) " ]
2015-05-26 22:15:52 +00:00
[ " $pre_push_hook " = " $( cat .git/hooks/pre-push) " ]
2017-01-02 13:07:53 +00:00
[ " $post_checkout_hook " = " $( cat .git/hooks/post-checkout) " ]
2017-01-02 14:36:28 +00:00
[ " $post_commit_hook " = " $( cat .git/hooks/post-commit) " ]
2017-01-02 16:56:47 +00:00
[ " $post_merge_hook " = " $( cat .git/hooks/post-merge) " ]
2015-09-17 22:26:02 +00:00
hooks: mention core.hookspath instead of just .git/hooks
In some cases, users may use `core.hooksPath` to locate their hooks in a
different location. However, right now, our hook and installation
instructions mention only `.git/hooks`.
We can update the instructions without a problem, but we don't want to
hard-code the hook path into the hooks themselves because of things like
symlinks and moved repository, plus the fact that we can't update a hook
automatically unless it's identical minus some whitespace changes. To
avoid spuriously failing to update a hook, let's print the right
location with the instructions, and just mention `core.hookspath` and
`.git/hooks` in the message, leaving it to the user to discover.
Note that technically, core.hookspath was not implemented until Git
2.9.0. However, while we still support older versions of Git, no
presently supported version of Ubuntu or Debian offers a version older
than 2.11, so the risk of practical confusion by mentioning this is low.
Nevertheless, make our tests pass by checking for an old Git explicitly.
2023-01-04 19:48:38 +00:00
# test manual steps with core.hookspath
gitversion = $( git version | cut -d" " -f3)
set +e
compare_version " $gitversion " 2.9.0
result = $?
set -e
if [ " $result " -ne " $VERSION_LOWER " ]
then
mkdir hooks
rm -fr .git/hooks
git config core.hookspath hooks
echo "test" > hooks/pre-push
echo "test" > hooks/post-checkout
echo "test" > hooks/post-commit
echo "test" > hooks/post-merge
expected = " Add the following to 'hooks/pre-push':
#!/bin/sh
command -v git-lfs >/dev/null 2>& 1 || { echo >& 2 \" \n This repository is configured for Git LFS but 'git-lfs' was not found on your path. If you no longer wish to use Git LFS, remove this hook by deleting the 'pre-push' file in the hooks directory ( set by 'core.hookspath' ; usually '.git/hooks' ) .\n \" ; exit 2; }
git lfs pre-push \" \$ @\"
Add the following to 'hooks/post-checkout' :
#!/bin/sh
command -v git-lfs >/dev/null 2>& 1 || { echo >& 2 \" \n This repository is configured for Git LFS but 'git-lfs' was not found on your path. If you no longer wish to use Git LFS, remove this hook by deleting the 'post-checkout' file in the hooks directory ( set by 'core.hookspath' ; usually '.git/hooks' ) .\n \" ; exit 2; }
git lfs post-checkout \" \$ @\"
Add the following to 'hooks/post-commit' :
#!/bin/sh
command -v git-lfs >/dev/null 2>& 1 || { echo >& 2 \" \n This repository is configured for Git LFS but 'git-lfs' was not found on your path. If you no longer wish to use Git LFS, remove this hook by deleting the 'post-commit' file in the hooks directory ( set by 'core.hookspath' ; usually '.git/hooks' ) .\n \" ; exit 2; }
git lfs post-commit \" \$ @\"
Add the following to 'hooks/post-merge' :
#!/bin/sh
command -v git-lfs >/dev/null 2>& 1 || { echo >& 2 \" \n This repository is configured for Git LFS but 'git-lfs' was not found on your path. If you no longer wish to use Git LFS, remove this hook by deleting the 'post-merge' file in the hooks directory ( set by 'core.hookspath' ; usually '.git/hooks' ) .\n \" ; exit 2; }
git lfs post-merge \" \$ @\" "
[ " $expected " = " $( git lfs update --manual 2>& 1) " ]
[ "test" = " $( cat hooks/pre-push) " ]
[ "test" = " $( cat hooks/post-checkout) " ]
[ "test" = " $( cat hooks/post-commit) " ]
[ "test" = " $( cat hooks/post-merge) " ]
# force replace unexpected hook
[ "Updated Git hooks." = " $( git lfs update --force) " ]
[ " $pre_push_hook " = " $( cat hooks/pre-push) " ]
[ " $post_checkout_hook " = " $( cat hooks/post-checkout) " ]
[ " $post_commit_hook " = " $( cat hooks/post-commit) " ]
[ " $post_merge_hook " = " $( cat hooks/post-merge) " ]
test -d .git/hooks && exit 1
fi
2015-10-26 23:12:15 +00:00
has_test_dir || exit 0
2015-09-30 23:38:13 +00:00
2015-09-17 22:26:02 +00:00
echo "test with bare repository"
cd ..
git clone --mirror without-pre-push bare
cd bare
2015-09-17 22:37:25 +00:00
git lfs env
2015-09-17 22:26:02 +00:00
git lfs update
2015-09-17 22:37:25 +00:00
ls -al hooks
2015-09-17 22:26:02 +00:00
[ " $pre_push_hook " = " $( cat hooks/pre-push) " ]
2015-05-26 21:49:04 +00:00
)
end_test
2015-09-02 19:25:34 +00:00
2017-07-06 18:59:20 +00:00
begin_test "update with leading spaces"
(
set -e
reponame = "update-leading-spaces"
git init " $reponame "
cd " $reponame "
2022-01-29 00:44:16 +00:00
[ "Updated Git hooks." = " $( git lfs update) " ]
2017-07-06 18:59:20 +00:00
# $pre_push_hook contains leading TAB '\t' characters
pre_push_hook = " #!/bin/sh
2022-01-27 07:40:54 +00:00
command -v git-lfs >/dev/null 2>& 1 || { echo >& 2 \" \\ nThis repository is configured for Git LFS but 'git-lfs' was not found on your path. If you no longer wish to use Git LFS, remove this hook by deleting '.git/hooks/pre-push' .\\ n\" ; exit 2; }
2017-07-06 18:59:20 +00:00
git lfs pre-push \" \$ @\" "
echo -n " $pre_push_hook " > .git/hooks/pre-push
2022-01-29 00:44:16 +00:00
[ "Updated Git hooks." = " $( git lfs update) " ]
2017-07-06 18:59:20 +00:00
)
end_test
2015-09-02 19:25:34 +00:00
begin_test "update lfs.{url}.access"
(
set -e
mkdir update-access
cd update-access
git init
git config lfs.http://example.com.access private
git config lfs.https://example.com.access private
git config lfs.https://example2.com.access basic
git config lfs.https://example3.com.access other
[ "private" = " $( git config lfs.http://example.com.access) " ]
[ "private" = " $( git config lfs.https://example.com.access) " ]
[ "basic" = " $( git config lfs.https://example2.com.access) " ]
[ "other" = " $( git config lfs.https://example3.com.access) " ]
2022-01-29 00:44:16 +00:00
expected = " Updated Git hooks.
2015-09-02 19:25:34 +00:00
Updated http://example.com access from private to basic.
Updated https://example.com access from private to basic.
Removed invalid https://example3.com access of other."
)
end_test
2015-09-08 15:29:53 +00:00
begin_test "update: outside git repository"
(
2015-10-19 20:47:18 +00:00
if [ -d "hooks" ] ; then
ls -al
echo "hooks dir exists"
exit 1
fi
2015-09-08 16:20:52 +00:00
set +e
git lfs update 2>& 1 > check.log
res = $?
2015-09-08 15:29:53 +00:00
set -e
2015-10-19 20:47:18 +00:00
2015-09-08 20:12:51 +00:00
if [ " $res " = "0" ] ; then
2015-10-19 20:47:18 +00:00
if [ -z " $GIT_LFS_TEST_DIR " ] ; then
echo " Passes because $GIT_LFS_TEST_DIR is unset. "
exit 0
fi
2015-09-08 20:12:51 +00:00
fi
2015-10-19 20:47:18 +00:00
2015-09-08 16:20:52 +00:00
[ " $res " = "128" ]
2015-10-19 20:47:18 +00:00
if [ -d "hooks" ] ; then
ls -al
echo "hooks dir exists"
exit 1
fi
cat check.log
2022-01-29 00:44:16 +00:00
grep "Not in a Git repository" check.log
2015-09-08 15:29:53 +00:00
)
end_test