
- Gerrit Tutorial
- Gerrit - Home
- Gerrit - Overview
- Setting up Git
- Installation
- Configure Git
- Set Your Username & Email
- Set Up SSH Keys in Gerrit
- Generate New SSH Key
- Add Your SSH Key
- Add SSH Key to your Gerrit Account
- Add SSH Key to use with Git
- Download Extension Using Git
- Prepare to work with Gerrit
- Installing Git-Review
- Configuring Git-Review
- Setting up Git-Review
- How to Submit a Patch
- Gerrit - Update Master
- Gerrit - Create Branch
- Make & Commit Your Change
- Prepare Push change set to Gerrit
- Push your change set to Gerrit
- View the Change / Next Steps
- Editing via the Web-Interface
- How Code is reviewed in Gerrit
- Review Before Merge
- Gerrit - Project Owners
- How to Comment on, review, merge
- Gerrit Useful Resources
- Gerrit - Quick Guide
- Gerrit - Useful Resources
- Gerrit - Discussion
- Selected Reading
- UPSC IAS Exams Notes
- Developer's Best Practices
- Questions and Answers
- Effective Resume Writing
- HR Interview Questions
- Computer Glossary
- Who is Who
Gerrit - Setting Up Git-Review
Git-review can be used to send git branches to Gerrit for reviewing. You can set up gitreview using the following command in the project directory.
$ git review -s
Git-review can be used as the command line tool for configuring Git clone, submitting the branches to Gerrit, fetching the existing files, etc. Git-review looks for the remote named gerrit for working with Gerrit by default.
If git-review finds the Gerrit remote, then it will submit the branch to HEAD:refs/for/master at the remote location and if there is no Gerrit remote access, then git-review looks for the .gitreview file at the root of the repository along with the gerrit remote information.
Git-review processes the following internally −
It will check whether the remote repository works or not for submitting the branches.
If there is no Gerrit remote access, then it will ask for the username and try to access the repository again.
It will create a remote access called gerrit that points to Gerrit.
It will install the commit-msg hook.