I’ve created a base/starter project with files commonly used for Github open source projects that is intended for extension by other projects. It also comes with commitlint and husky for linting commits.
So if someone clones it and runs the following the commits get linted.
git clone [email protected]:fireflysemantics/fs-github-flow-docs-starter.git
cd fs-github-flow-docs-starter/
npm i && npx husky init
echo "" > .husky/pre-commit
git add . && git commit -m "linting error"
⧗ input: linting error
✖ subject may not be empty [subject-empty]
✖ type may not be empty [type-empty]
✖ found 2 problems, 0 warnings
ⓘ Get help: https://github.com/conventional-changelog/commitlint/#what-is-commitlint
husky - commit-msg script failed (code 1)
I was wondering if there is a way to get it to work without have to rerun npx husky init? So that users could just do:
git clone [email protected]:fireflysemantics/fs-github-flow-docs-starter.git
cd fs-github-flow-docs-starter/
npm i
git add . && git commit -m "linting error"
⧗ input: linting error
✖ subject may not be empty [subject-empty]
✖ type may not be empty [type-empty]
✖ found 2 problems, 0 warnings
ⓘ Get help: https://github.com/conventional-changelog/commitlint/#what-is-commitlint
husky - commit-msg script failed (code 1)
Thoughts?