office-gobmx

History

Mike Kaganski 18ff318c75 Revert "Drop allownonascii check from pre-commit checks" This reverts commit `8a0015c35f`. See https://lists.freedesktop.org/archives/libreoffice/2023-December/091265.html for details. Change-Id: I9bfa893af935587c7a4681e71b13a734d5f50b5b Reviewed-on: https://gerrit.libreoffice.org/c/core/+/160177 Tested-by: Jenkins Reviewed-by: Mike Kaganski <mike.kaganski@collabora.com>		2023-12-02 21:55:33 +01:00
..
commit-msg	Restore .git-hooks/commit-msg	2023-03-08 10:37:00 +00:00
post-merge	git-hooks: post-merge script does not need /bin/bash	2015-02-13 16:40:36 +01:00
pre-commit	Revert "Drop allownonascii check from pre-commit checks"	2023-12-02 21:55:33 +01:00
README	git-hooks: better handling in './g -z' with win-links	2023-03-22 10:44:24 +00:00

README

Git hooks are executable scripts you can place in $GIT_DIR/hooks directory to trigger action at certain points.

To install manually, run:

  cd .git/hooks && ln -s ../../.git-hooks/* ./
  
When you using GIT for Windows, you need Windows links
Open a Dos-Box with admin rights then
  cd .git/hooks
  FOR /F " usebackq " %i IN (`dir /b ..\..\.git-hooks`) DO del /as /f %i & del %i & mklink %i ..\..\.git-hooks\%i
the error 'Could Not Find ...' can be ignore

There are two groups of these hooks: client side and server side.

The client-side hooks:
are for client operations such as committing and merging.

The server-side hooks:
are for Git server operations such as receiving pushed commits.

See Also [ http://git-scm.com/book/en/Customizing-Git-Git-Hooks ]