Drawwell/SandpointsGitHook
Drawwell/SandpointsGitHook
3
0
Fork 0
Code Issues Pull requests Releases Wiki Activity

stupid typo..

Browse source
This commit is contained in:
Marcell Mars 2020-12-03 00:57:02 +01:00
parent 513cf36e95
commit 20944139f6
1 changed files with 1 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
README.md
View file

@ -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)\`}`.