| David Shevitz | 42135f9 | 2017-07-13 09:52:28 -0700 | [diff] [blame] | 1 | = How Gerrit Works |
| 2 | |
| 3 | To understand how Gerrit fits into and enhances the developer workflow, consider |
| 4 | a typical project. This project has a central source repository, which serves as |
| 5 | the authoritative copy of the project's contents. |
| 6 | |
| 7 | .Central Source Repository |
| 8 | image::images/intro-quick-central-repo.png[Authoritative Source Repository] |
| 9 | |
| 10 | Gerrit takes the place of this central repository and adds an additional |
| 11 | concept: a _store of pending changes_. |
| 12 | |
| 13 | .Gerrit in place of Central Repository |
| 14 | image::images/intro-quick-central-gerrit.png[Gerrit in place of Central Repository] |
| 15 | |
| 16 | With Gerrit, when a developer makes a change, it is sent to this store of |
| 17 | pending changes, where other developers can review, discuss and approve the |
| 18 | change. After enough reviewers grant their approval, the change becomes an |
| 19 | official part of the codebase. |
| 20 | |
| 21 | In addition to this store of pending changes, Gerrit captures notes |
| 22 | and comments about each change. These features allow developers to review |
| 23 | changes at their convenience, or when conversations about a change can't |
| 24 | happen face to face. They also help to create a record of the conversation |
| 25 | around a given change, which can provide a history of when a change was made and |
| 26 | why. |
| 27 | |
| 28 | Like any repository hosting solution, Gerrit has a powerful |
| 29 | link:access-control.html[access control model]. This model allows you to |
| 30 | fine-tune access to your repository. |
| 31 | |
| 32 | GERRIT |
| 33 | ------ |
| 34 | Part of link:index.html[Gerrit Code Review] |
| 35 | |
| 36 | SEARCHBOX |
| 37 | --------- |
