Samuel Degueldre
92497ed4f1
In #86163 we added a check on the branch name to avoid running the tooling on stable branches, however this check used bash-specific syntax. While the hashbang in the pre-commit hook specifies that the hook should be run using bash, we were using the npm module "husky" to manage git hooks, which would ignore this hashbang and always run the hook using sh, causing the hook to fail in all cases. After some consideration, we have decided to stop using husky, as its main purpose is to make hook management easier in npm-based projects. Since we already need a script to enable the tooling, we can do essentially the same thing that husky is doing but with more control over the process with no drawbacks. closes odoo/odoo#87436 X-original-commit: 3104ab16ecf88d4f7b1618db4d62e7f57df34e6c Signed-off-by: Simon Genin (ges@odoo) <ges@odoo.com>
35 lines
866 B
Bash
Executable File
35 lines
866 B
Bash
Executable File
#!/bin/bash
|
|
community=$(cd -- "$(dirname "$0")" &> /dev/null && cd ../../.. && pwd)
|
|
|
|
disableInDir () {
|
|
cd "$1"
|
|
git config --unset core.hooksPath
|
|
rm .eslintignore
|
|
rm .prettierignore
|
|
rm .eslintrc.json
|
|
rm .prettierrc.json
|
|
rm package.json
|
|
rm package-lock.json
|
|
rm -r node_modules
|
|
cd - &> /dev/null
|
|
}
|
|
|
|
read -p "Do you want to delete the tooling installed in enterprise too ? [y, n]" willingToDeleteToolingInEnterprise
|
|
if [[ $willingToDeleteToolingInEnterprise != "n" ]]
|
|
then
|
|
read -p "What is the relative path from community to enterprise ? (../enterprise)" pathToEnterprise
|
|
pathToEnterprise=${pathToEnterprise:-../enterprise}
|
|
fi
|
|
|
|
disableInDir "$community"
|
|
|
|
if [[ $willingToDeleteToolingInEnterprise != "n" ]]
|
|
then
|
|
disableInDir "$pathToEnterprise"
|
|
fi
|
|
|
|
|
|
echo ""
|
|
echo "JS tooling have been removed from the roots"
|
|
echo ""
|