38 lines
1 KiB
Markdown
38 lines
1 KiB
Markdown
# Developer Guide
|
|
|
|
[TOC]
|
|
|
|
## Code Review
|
|
|
|
This project uses Gerrit for code review:
|
|
https://gerrit-review.googlesource.com/
|
|
which uses the ["git push" workflow][1] with server
|
|
https://gerrit.googlesource.com/gerrit-monitoring. You will need a
|
|
[generated cookie][2].
|
|
|
|
[1]: https://gerrit-review.googlesource.com/Documentation/user-upload.html#_git_push
|
|
[2]: https://gerrit.googlesource.com/new-password
|
|
|
|
Gerrit depends on "Change-Id" annotations in your commit message.
|
|
If you try to push a commit without one, it will explain how to
|
|
install the proper git-hook:
|
|
|
|
```
|
|
curl -Lo `git rev-parse --git-dir`/hooks/commit-msg \
|
|
https://gerrit-review.googlesource.com/tools/hooks/commit-msg
|
|
chmod +x `git rev-parse --git-dir`/hooks/commit-msg
|
|
```
|
|
|
|
Before you create your local commit (which you'll push to Gerrit)
|
|
you will need to set your email to match your Gerrit account:
|
|
|
|
```
|
|
git config --local --add user.email foo@bar.com
|
|
```
|
|
|
|
Normally you will create code reviews by pushing for master:
|
|
|
|
```
|
|
git push origin HEAD:refs/for/master
|
|
```
|