Submitting your first patch
Setting up git and ssh
(to work smoothly with Gerrit.)
Generate a personal dedicated public / private key set.
ssh-keygen -t rsa -f ~/.ssh/jami_gerrit_review_rsa`
Your identification has been saved in
jami_gerrit_review_rsa. Your public key has been saved in
Tell gerrit your public key
Set up your local ssh (via
Test all of the above (ssh on the service or just try to clone a repo on gerrit via ssh)
This assumes you have moved any existing project clone out of the way.
Clone a (fresh) copy of the project.
git clone ssh://USERNAME@review.jami.net:29420/PROJECT_NAME_GOES_HERE.git; e.g.
git clone ssh://email@example.com:29420/jami-project.git.
Configure this clones local .git/config (optional)
Generate commit Change-Ids aka: commit-msg hook script
A shell script, to be installed to .git/hooks/commit-msg.
The script creates a unique Change_Id:hash for each commit made from your repository.
The first time you attempt a push to review
git push origin HEAD:refs/for/master, gerrit will notice a lack of Change-Id.
Gerrit will also present a secure copy (scp) string. Use that to download a copy of .git/hooks/commit-msg.
Original author: Peter Gossner