From 20944139f6d5d955d25e53442c0efcdd2642186d Mon Sep 17 00:00:00 2001 From: Marcell Mars Date: Thu, 3 Dec 2020 00:57:02 +0100 Subject: [PATCH] stupid typo.. --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 9c3b897..c6e8d6c 100644 --- a/README.md +++ b/README.md @@ -32,7 +32,7 @@ change it there and rebuild it. `sphook` should work as it is for two scenarios: - _bare_ git repository and in our case we run it against the `gitea` instances (git web frontend). - - Gitea keeps its `post-receive` hooks inside the `hooks/post-receive.d/` directory relative to particular _bare_ git repository. `sphooks` should land there as it is, no need to change the name, and it will run after every remote `git push` into the repo. + - Gitea keeps its `post-receive` hooks inside the `hooks/post-receive.d/` directory relative to particular _bare_ git repository. `sphook` should land there as it is, no need to change the name, and it will run after every remote `git push` into the repo. - _working_ git repository - that's usually a contributor running the local instance of a git repository. In order for `sphinx` to work as `post-commit` hook it should be placed inside `.git/hooks/` directory, renamed to `post-commit` and made executable (`chmod +x post-commit`). Hugo, via that hook, will render its output into: `/var/www/html/sandpoints/{hugo_project_name}-{`\`crc32.ChecksumIEEE(git_repo_path)\`}`.