Skip to content
Snippets Groups Projects
Commit 23352dec authored by Dmitri Naumov's avatar Dmitri Naumov
Browse files

[hooks] Remove failing file-names hook.

The hook is failing sporadically for yet unknown reason.
This is partial revert of f95ce87a [hooks] Added file name check.
parent b5e2ea4f
No related branches found
No related tags found
No related merge requests found
......@@ -22,11 +22,6 @@ repos:
language: system
files: '.*\.cpp'
stages: [commit, manual]
- id: file-names
name: Check file names
entry: scripts/hooks/pre-commit-file-names.sh
language: system
stages: [commit, manual]
- id: git-lfs
name: Check git lfs files
entry: scripts/hooks/pre-commit-git-lfs.sh
......
#!/usr/bin/env bash
if git rev-parse --verify HEAD >/dev/null 2>&1
then
against=HEAD
else
# Initial commit: diff against an empty tree object
against=4b825dc642cb6eb9a060e54bf8d69288fbee4904
fi
# If you want to allow non-ASCII filenames set this variable to true.
allownonascii=$(git config --bool hooks.allownonascii)
# Redirect output to stderr.
exec 1>&2
# Cross platform projects tend to avoid non-ASCII filenames; prevent
# them from being added to the repository. We exploit the fact that the
# printable range starts at the space character and ends with tilde.
if [ "$allownonascii" != "true" ] &&
# Note that the use of brackets around a tr range is ok here, (it's
# even required, for portability to Solaris 10's /usr/bin/tr), since
# the square bracket bytes happen to fall in the designated range.
test $($@ |
LC_ALL=C tr -d '[ -~]\0' | wc -c) != 0
then
cat <<\EOF
Error: Attempt to add a non-ASCII file name.
This can cause problems if you want to work with people on other platforms.
To be portable it is advisable to rename the file.
If you know what you are doing you can disable this check using:
git config hooks.allownonascii true
EOF
exit 1
fi
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment