Skip to content

Commit eb3fee1

Browse files
bmeckjasnell
authored andcommitted
doc: ensure collaborators validate commits
This should be done every time a collaborator pushes a commit. PR-URL: #16162 Reviewed-By: Joyee Cheung <[email protected]> Reviewed-By: Anna Henningsen <[email protected]> Reviewed-By: Luigi Pinca <[email protected]> Reviewed-By: Roman Reiss <[email protected]> Reviewed-By: Jeremiah Senkpiel <[email protected]> Reviewed-By: Tobias Nießen <[email protected]> Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Michael Dawson <[email protected]> Reviewed-By: Gibson Fahnestock <[email protected]> Reviewed-By: Evan Lucas <[email protected]>
1 parent 4faa231 commit eb3fee1

File tree

1 file changed

+7
-0
lines changed

1 file changed

+7
-0
lines changed

COLLABORATOR_GUIDE.md

+7
Original file line numberDiff line numberDiff line change
@@ -517,6 +517,13 @@ Run tests (`make -j4 test` or `vcbuild test`). Even though there was a
517517
successful continuous integration run, other changes may have landed on master
518518
since then, so running the tests one last time locally is a good practice.
519519

520+
Validate that the commit message is properly formatted using
521+
[core-validate-commit](https://github.com/evanlucas/core-validate-commit).
522+
523+
```text
524+
$ git rev-list upstream/master...HEAD | xargs core-validate-commit
525+
```
526+
520527
Time to push it:
521528

522529
```text

0 commit comments

Comments
 (0)