lint: Rename commit_messages to gitlint.

Use `gitlint` name to register gitlint linter since it is the commonly
used name for it.
This commit is contained in:
Aman Agrawal 2019-06-18 19:57:47 +05:30 committed by Tim Abbott
parent 6b73926e93
commit cf8653945f
2 changed files with 2 additions and 2 deletions

View File

@ -117,7 +117,7 @@ something valuable to helping keep Zulip bug-free.
- Or, when running the test suite, if you get an error involving Git that looks like this:
```
commit_messages| An error occurred while executing '/usr/bin/git rev-list --max-count=-1 upstream/master..HEAD': b"fatal: ambiguous argument 'upstream/master..HEAD': unknown revision or path not in the working tree.\nUse '--' to separate paths from revisions, like this:\n'git <command> [<revision>...] -- [<file>...]'"
gitlint| An error occurred while executing '/usr/bin/git rev-list --max-count=-1 upstream/master..HEAD': b"fatal: ambiguous argument 'upstream/master..HEAD': unknown revision or path not in the working tree.\nUse '--' to separate paths from revisions, like this:\n'git <command> [<revision>...] -- [<file>...]'"
```
... then you may need to connect the Zulip upstream repository with the following command:

View File

@ -98,7 +98,7 @@ def run():
# Disabled check for imperative mood until it is stabilized
if 'gitlint' not in args.skip:
linter_config.external_linter('commit_messages', ['tools/commit-message-lint'])
linter_config.external_linter('gitlint', ['tools/commit-message-lint'])
@linter_config.lint
def custom_py():