Gerrit Tutorial: Changes, Patch Sets and Review Labels
Gerrit organizes code review around changes with successive patch sets. A revised commit can update the proposal without creating an unrelated discussion when its identity is handled appropriately. This tutorial explains that model through review references, change identifiers and submission conditions. You will distinguish a patch set from a separate branch and connect feedback to the version currently under review. Review identity and Git commit identity play related but different roles.
Here's a popular Gerrit video — watch it, then summarize it with one click. Or paste any other YouTube link below.
— or paste your own YouTube link —
Want to keep the key points from a YouTube video? Paste the link below to turn it into structured notes.
Why Use Gerrit Tutorial: Changes, Patch Sets and Review Labels
- Recognize one change across revised patch sets
- Understand the purpose of review identity
- Identify the patch set being assessed
- Interpret labels and submission conditions
- Follow a submitted change into target history
Frequently Asked Questions
What is a patch set?
A patch set is a particular revision of a Gerrit change under review. Later patch sets can address feedback while retaining the proposal's review context. Check the current patch set when interpreting comments or validation evidence.
Is a Change-Id the same as a commit hash?
A Change-Id supports Gerrit's association of revisions with a review change. A commit hash identifies a specific Git object. Revised commits can therefore have different hashes while remaining connected to the same review proposal.
Why use a review reference when pushing?
Gerrit uses its review workflow to receive proposed changes separately from direct target-branch updates. The intended push destination matters. Publishing a commit to an arbitrary reference does not guarantee it enters the correct review process.
Does a positive review label guarantee immediate submission?
Submission depends on the applicable project requirements, which can include several labels or conditions. One favorable assessment is evidence toward readiness. Inspect the current change's requirements before assuming target history already contains it.
What should be checked after revising a change?
Confirm that the new patch set belongs to the intended review and inspect its differences. Relevant checks and comments need context for that revision. The continuing discussion does not make earlier evidence automatically valid for every update.