CONTRIBUTING: Document gerrit quirks
Document how to obtain the commit-msg hook and how to push a change for review.
Change-Id: If39e98e2fc20be549a08c88839b4d96a8ab7935b
Reviewed-on: https://dawn-review.googlesource.com/c/tint/+/78784
Auto-Submit: Ben Clayton <bclayton@google.com>
Kokoro: Kokoro <noreply+kokoro@google.com>
Reviewed-by: David Neto <dneto@google.com>
Commit-Queue: David Neto <dneto@google.com>
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index afbb556..4d59e35 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -22,6 +22,23 @@
Submissions should follow the [Tint style guide](docs/style_guide.md).
+## Pushing to Gerrit
+
+Each change requires a `Change-Id` field in the commit message, which is generated by the [Gerrit commit-msg hook](](https://gerrit-review.googlesource.com/Documentation/cmd-hook-commit-msg.html)). \
+In a bash terminal, with the current path set to your tint source tree, this can be obtained by running the following:
+
+```bash
+f=`git rev-parse --git-dir`/hooks/commit-msg ; mkdir -p $(dirname $f) ; curl -Lo $f https://gerrit-review.googlesource.com/tools/hooks/commit-msg ; chmod +x $f
+```
+
+If you've already locally committed a change without the `Change-Id`, running `git commit --amend` will add the missing `Change-Id`.
+
+To create a Gerrit change for review, type:
+
+```bash
+git push origin HEAD:refs/for/main
+```
+
## Community Guidelines
This project follows
