git-lfs/test/test-install-custom-hooks-path.sh

#!/usr/bin/env bash

. "test/testlib.sh"

# These tests rely on behavior found in 2.9.0 to perform themselves,
# specifically:
#   - core.hooksPath support
ensure_git_version_isnt $VERSION_LOWER "2.9.0"

begin_test "install with supported core.hooksPath"
(
  set -e

  repo_name="supported-custom-hooks-path"
  git init "$repo_name"
  cd "$repo_name"

  hooks_dir="custom_hooks_dir"
  mkdir -p "$hooks_dir"

  git config --local core.hooksPath "$hooks_dir"

  git lfs install 2>&1 | tee install.log
  grep "Updated pre-push hook" install.log

  [ -e "$hooks_dir/pre-push" ]
)
end_test
lfs/hook: teach `lfs.Hook` about `core.hooksPath` This commit gives the `lfs.Hook` knowledge of the new `core.hooksPath` configuration value that was introduce in Git 2.9.0. When `core.HooksPath` is found in the Git configuration AND is supported (i.e., installed Git binary has a version greater than or equal to "2.9.0"), `git-lfs install` will place new hooks in that directory. If the `core.hooksPath` is specified, but the installed verison of Git does NOT support it, then it will be ignored and installed in `.git/hooks` as per usual. To test this behavior, two new shell tests were added: - One that runs on Git >= 2.9.0, and tests that `core.hooksPath` is respected - One that runs on Git < 2.9.0, and tests that `core.hooksPath` is ignored Unfortunately, our current testing framework does not support skipping individual tests, only skipping entire files, so two new shell test files were added. Resolves github/git-lfs#1407. 2016-08-01 21:47:54 +00:00			`#!/usr/bin/env bash`

			`. "test/testlib.sh"`

test: s/preform/perfom/g 2016-08-02 15:35:51 +00:00			`# These tests rely on behavior found in 2.9.0 to perform themselves,`
lfs/hook: teach `lfs.Hook` about `core.hooksPath` This commit gives the `lfs.Hook` knowledge of the new `core.hooksPath` configuration value that was introduce in Git 2.9.0. When `core.HooksPath` is found in the Git configuration AND is supported (i.e., installed Git binary has a version greater than or equal to "2.9.0"), `git-lfs install` will place new hooks in that directory. If the `core.hooksPath` is specified, but the installed verison of Git does NOT support it, then it will be ignored and installed in `.git/hooks` as per usual. To test this behavior, two new shell tests were added: - One that runs on Git >= 2.9.0, and tests that `core.hooksPath` is respected - One that runs on Git < 2.9.0, and tests that `core.hooksPath` is ignored Unfortunately, our current testing framework does not support skipping individual tests, only skipping entire files, so two new shell test files were added. Resolves github/git-lfs#1407. 2016-08-01 21:47:54 +00:00			`# specifically:`
			`# - core.hooksPath support`
			`ensure_git_version_isnt $VERSION_LOWER "2.9.0"`

			`begin_test "install with supported core.hooksPath"`
			`(`
			`set -e`

			`repo_name="supported-custom-hooks-path"`
			`git init "$repo_name"`
			`cd "$repo_name"`

			`hooks_dir="custom_hooks_dir"`
			`mkdir -p "$hooks_dir"`

			`git config --local core.hooksPath "$hooks_dir"`

			`git lfs install 2>&1 \| tee install.log`
			`grep "Updated pre-push hook" install.log`

			`[ -e "$hooks_dir/pre-push" ]`
			`)`
			`end_test`