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.

Sign up for GitHub

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

Jump to bottom

docs: Added information on how to run the linter. #7534

Closed
wants to merge 6 commits into from
Closed

docs: Added information on how to run the linter. #7534

Changes from all commits
Commits
Show all changes
6 commits
Select commit Hold shift + click to select a range
a7923aa
docs: Added information on how to run the linter.
diosney Jul 4, 2016
390101b
docs: Added clarification about the linter.
diosney Jul 4, 2016
d85a388
docs: Added clarification about the linter execution.
diosney Jul 5, 2016
50e5745
docs: Linter line rewording.
diosney Jul 5, 2016
2f42d83
docs: Changed for consistent verb tense.
diosney Jul 5, 2016
6a61891
repl: Fixed post-final nit in`completer` function doc.
diosney Jul 6, 2016
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions CONTRIBUTING.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -150,6 +150,9 @@ $ ./configure && make -j8 test
Make sure the linter is happy and that all tests pass. Please, do not submit
patches that fail either check.

Running `make test` will run the linter as well unless one or more tests fail.
If you want to run the linter without running tests, use `make lint`.

If you are updating tests and just want to run a single test to check it, you
can use this syntax to run it exactly as the test harness would:

Expand Down