Try for free

Glossary

Code review terms, in plain words

LGTM means “looks good to me”: the reviewer approves. PTAL means “please take a look”. A nit is a small comment the author may skip. Few of these words can hold a merge on GitHub; the table below says which can.

We counted these words on 1,129 merged pull requests from 12 open-source projects on November 10, 2026: LGTM turned up on 265 of them, a nit on 80, PTAL on 9 and SGTM on 2.

LGTM
Looks good to me: the reviewer approves the change.[1] “LGTM with comments” approves it while leaving small points the author fixes before merging.[3] On GitHub the words alone approve nothing: only an Approve review counts toward required reviews.[10]
PTAL
Please take a look. An author sends it to ask for a review, and again after pushing fixes, when it means “please take another look”. On GitHub the same request is a button: the Re-request review icon next to a reviewer’s name.[4]
SGTM
Sounds good to me. Agreement with a plan or an answer in the thread, not an approval of the code.
Nit
Short for nitpick: a minor point, such as “nit: rename cnt to retryCount”. Google’s review guide labels these “Nit:”, worth doing but not hugely important, so the author knows it is optional.[2] Conventional Comments calls it “nitpick:”, a trivial, preference-based request that should not block.[9] A formatting nit is one a linter can make instead.
WIP and RFC
Work in progress: not ready for review yet. Request for comments: the author wants feedback on the approach before polishing the code.
ACK and NACK
Acknowledged and not acknowledged: agreement with a change, or an objection to it, as written on mailing-list projects.
Approve, Request changes, Comment
GitHub’s three review decisions. Approve says the change is ready to merge, Request changes flags feedback to address before merging, and Comment leaves feedback without either.[5] Administrators make approvals required with branch protection rules.[11]
Merge request vs pull request
The same thing under two names: a pull request on GitHub, a merge request on GitLab.[6][7] GitHub’s head and base branch are GitLab’s source and target. The name comes from git request-pull, which asks a maintainer to pull your branch.[8]
Blocking and non-blocking
Whether a comment must be resolved before the change is accepted. Conventional Comments adds a (blocking) or (non-blocking) tag to the comment.[9]
Stacked pull request
One of a chain of small pull requests, each based on the branch of the one below, so each can be reviewed and merged on its own.[12]
Rubber stamp
An approval given without really reading the change. A one-minute LGTM on a 2,000-line diff is usually one.
Draft pull request
A pull request marked not ready. It cannot be merged until it is marked ready for review.[6]
P0, P1, P2
IonWarp’s severities. P0 and P1 should be fixed before merging; a P2 is real but can wait, and the review lists it as a nitpick. By default a P0 sets IonWarp’s GitHub check to Action required.

Which terms block a merge on GitHub?

Typed words hold nothing on their own. Only a draft, a required review, a required check or, on a branch that asks for it, an open thread can hold a merge.

Which code review terms block a merge
TermOn GitHubIonWarp
LGTM, SGTM or PTAL in a commentHolds nothing; only an Approve review counts toward required reviews[10]Never approves; needs no PTAL
NitHolds nothing unless the branch requires conversation resolution[11]A P2 finding, listed as a nitpick
Request changes reviewBlocks only where a rule requires reviews; then that reviewer must approve, or the review be dismissed[11]Never submits one; a P0 sets the check instead
Draft pull requestCannot be merged[6]Skipped by default
Required status checkMust pass, be skipped or be neutral to merge[11]P0 is Action required, P1 Neutral, P2 Success

How often they show up

  • LGTM usually comes with a click: of the 265 pull requests with one, 96 were in Kubernetes. Elsewhere, a reviewer who wrote it also clicked Approve 182 times out of 190.
  • Nits rarely demand changes: of 160 nits left inside a review, 126 sat in a Comment review, 25 in an Approve, 7 in reviews since dismissed and 2 in Request changes.
  • The sample: up to 100 recently updated pull requests by human authors, merged since May 10, 2026, from each of Kubernetes, Rust, Node.js, React, VS Code, Django, Rails, PyTorch, Grafana, Terraform, Kafka and Elasticsearch. Bots, quotes and code left out. GitHub as a whole may look different.

Sources

  1. Google, Engineering Practices: terminology, read 2026-10-04.
  2. Google, How to write code review comments, read 2026-10-04.
  3. Google, Speed of code reviews, read 2026-10-04.
  4. GitHub Docs, Requesting a pull request review, read 2026-11-08.
  5. GitHub Docs, Pull request reviews, read 2026-10-04.
  6. GitHub Docs, About pull requests, read 2026-10-04.
  7. GitLab Docs, Merge requests, read 2026-10-04.
  8. Git, git-request-pull, read 2026-10-04.
  9. Conventional Comments, Conventional Comments, read 2026-11-03.
  10. GitHub Docs, Approving a pull request with required reviews, read 2026-11-10.
  11. GitHub Docs, About protected branches, read 2026-11-10.
  12. GitHub Docs, About stacked pull requests, read 2026-10-04.

FAQ

Quick answers

What does LGTM mean?

Looks good to me. A reviewer writes it to approve a pull request. On GitHub, only an Approve review counts toward required reviews; typing LGTM does not.

What does PTAL mean?

Please take a look. Authors use it to ask for a first review, and again after pushing fixes, when it reads as “please take another look”.

What does nit mean in code review?

A nit, short for nitpick, is a small, optional suggestion: a name, a comment, a formatting choice. Starting the comment with “nit:” tells the author it will not block the merge.

What does SGTM mean?

Sounds good to me. It agrees with a plan or an answer in a thread; unlike LGTM, it does not approve the code.

What is the difference between a pull request and a merge request?

Nothing but the name: GitHub says pull request, GitLab says merge request.

Get a reviewer that never rubber-stamps.

Try for free

14 days free, no card. Then Pro is $49 a month per workspace with 5 seats, or Max $149 with 10.