Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

refactor: easier commitlint command #1496

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
1 change: 1 addition & 0 deletions package.json
Expand Up @@ -92,6 +92,7 @@
"scripts": {
"docs": "typedoc",
"lint": "eslint src test --ext .js,.ts && tsc",
"lint:commit": "commitlint --from origin/master --to HEAD",
"test": "mocha test/unit test/unit/token test/unit/tracking-buffer",
"test-integration": "mocha test/integration/",
"test-all": "mocha test/unit/ test/unit/token/ test/unit/tracking-buffer test/integration/",
Expand Down
2 changes: 1 addition & 1 deletion pull_request_template.md
Expand Up @@ -4,6 +4,6 @@
3. After bug fix/code change, ensure all the existing tests and new tests (if any) pass (`npm run-script test-all`). During development, to run individual test use `node_modules/nodeunit test/<test_file.js> -t <test_name>`.
4. Build the driver (`npm run build`).
5. Run eslint and flow typechecker (`npm run lint`).
6. Run commitlint (`node_modules/.bin/commitlint --from origin/master --to HEAD`). Refer [commit conventions](https://commitlint.js.org/#/concepts-commit-conventions) and [commit rules](https://commitlint.js.org/#/reference-rules).
6. Run commitlint (`npm run lint:commit`). Refer [commit conventions](https://commitlint.js.org/#/concepts-commit-conventions) and [commit rules](https://commitlint.js.org/#/reference-rules).

**Thank you for Contributing!**