Starter
Try AI PR review.
- 2 reviewers
- Code Review
- Security Review
- 3 seats included
- 15,000 credits to start, then 5,000/mo
- Unlimited repos
LGTM means "looks good to me". It is what a code reviewer says when approving a change.[1]
In chat it means the same: you read it and agree. On GitHub an LGTM is only a comment; the approval that counts toward a branch's required reviews is the Approve review.[2]
LGTM is "what a code reviewer says when approving a CL", Google's word for one self-contained change.[1]
The Code-Review label spells it out: +2 is "Looks good to me, approved" and enables submit, +1 is "Looks good to me, but someone else must approve".[3]
A Code-Review +1 in Gerrit is also known as an LGTM, and the change needs a positive review from an owner of each directory it touches.[4]
A reviewer types /lgtm to add the lgtm label and an approver types /approve to add approved; a pull request needs both labels to merge.[5]
LGTM is text. Approve is the review state, and a pull request's author cannot approve their own pull request. With required reviews and stale review dismissal on, a new commit that changes code dismisses the approval.[2]
Approves the change and leaves small points the author fixes before merging.[6] A nit in those comments is optional.[7]
An approval given without reading the change. A one-minute LGTM on a 2,000-line diff is usually one.
IonWarp never approves a pull request. It posts its findings as one comment on the pull request, and by default a P0 finding sets its GitHub check to Action required. A person still gives the LGTM.
PTAL, nit, SGTM, WIP and the rest are in code review terms.
One workspace price with seats included. Credits pool across your team. Unlimited repos on every plan.
Try AI PR review.
Get AI PR review right from day 1.
Scale AI PR review.
Custom reviewers + credits · GitHub Enterprise · SSO/SAML + audit logs · Custom security review + SLA
Looks good to me. A code reviewer writes it to approve a change; in chat it means you read something and agree.
No. GitHub counts the Approve review, not the words. A required-reviews rule needs an Approve from someone other than the author.
The reviewer approves, and leaves a few small, optional suggestions. The author can fix them before merging or skip them.
LGTM approves the code. SGTM, sounds good to me, agrees with a plan or an answer in the thread, not with the code itself.
It adds the lgtm label to the pull request. An approver's /approve adds the approved label, and the pull request needs both to merge.