Skip to content

Commit

Permalink
doc: ensure collaborators validate commits
Browse files Browse the repository at this point in the history
This should be done every time a collaborator pushes a commit.
  • Loading branch information
bmeck committed Oct 12, 2017
1 parent a36aa04 commit bf3d990
Showing 1 changed file with 6 additions and 0 deletions.
6 changes: 6 additions & 0 deletions COLLABORATOR_GUIDE.md
Original file line number Diff line number Diff line change
Expand Up @@ -517,6 +517,12 @@ Run tests (`make -j4 test` or `vcbuild test`). Even though there was a
successful continuous integration run, other changes may have landed on master
since then, so running the tests one last time locally is a good practice.

Validate that the commit message is properly formatted using [core-validate-commit](https://github.com/evanlucas/core-validate-commit).

```text
$ core-validate-commit
```

Time to push it:

```text
Expand Down

0 comments on commit bf3d990

Please sign in to comment.