office-gobmx

History

Mike Kaganski 8a0015c35f Drop allownonascii check from pre-commit checks Supposedly, at this day and age, it is OK to use non-ascii file names. Specifically, this is intended to allow such names for bugdocs, which allows simpler testing of problems with handling those. An alternative would be to rename bugdocs at runtime; but that still requires that the target filesystem supports such names, so... Change-Id: I25da2402f311d59c5777c4cd302147d6965dea5f Reviewed-on: https://gerrit.libreoffice.org/c/core/+/160217 Tested-by: Jenkins Reviewed-by: Mike Kaganski <mike.kaganski@collabora.com>		2023-12-01 16:13:32 +01:00
..
commit-msg	Restore .git-hooks/commit-msg	2023-03-08 10:37:00 +00:00
post-merge
pre-commit	Drop allownonascii check from pre-commit checks	2023-12-01 16:13:32 +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 ]