SGTM meaning: “sounds good to me”, and why it is not LGTM
SGTM means “sounds good to me”.[1] In a code review thread it agrees with a plan, an answer or a suggested change. It does not say the code is ready: that is LGTM, and on GitHub only an Approve review counts toward required reviews.[2]
It is rare on pull requests. On 1,129 merged pull requests from 12 open-source projects, counted on November 10, 2026, SGTM appeared on 2, against 265 for LGTM and 9 for PTAL.[3] You meet it earlier, in issues, proposals, design docs and chat, where a plan gets agreed before the code exists. The Go project’s code review wiki lists it beside LGTM and PTAL as a term reviewers use.[4]
Updated
SGTM in real threads
“SGTM. I adjusted CL 758981 with your suggestion.”
Go proposal #78339, on adding Filetime.Unix to Go’s Windows packages. Another participant described how the function should behave; the author agreed and changed the code in the same reply.[5] The SGTM agrees with the behavior. Reviewing the code is a separate step.
“SGTM”, to a plan
Go issue #37561, on flags for the gorelease tool. To “I’d rather hold off on -json and -f until basically everything else is done”, the contributor answered with one word.[6] Agreement on the order of work, before any code.
In a design doc (an example): “Option B, a queue per workspace, SGTM. Can we cap it at 1,000 jobs?”
Agreement with a condition attached. Answer the condition before you treat the plan as settled.
In Slack (an example): “Ship it Thursday after the freeze?” “SGTM.”
A plan, a time, a yes. Nobody read code here, and nobody needed to.
On a pull request, where it is the wrong word
Under a diff, “SGTM” reads as agreement with something, not as an approval. If you read the code and want it merged, submit an Approve review and say LGTM. If you agree with an answer in a thread, SGTM is right, and the thread can be resolved.
How to use SGTM, and how to answer one
Use it for plans and answers
A design, a deploy time, a reply to “should this be its own pull request?”. For code you have read, use LGTM with an Approve review.
Say the condition
“SGTM if we keep the old endpoint for one release” agrees and names the catch in one line.
Do not merge on it
An SGTM on a pull request is a comment. Where the branch requires reviews, it needs an Approve from someone other than the author.[2] Ask that person to approve, or re-request their review.[7]
Answer by doing it
“Done in 4be21c0” closes the loop, and the thread can be resolved. If the SGTM came with a condition, say how you met it.
An agreed plan still needs the code read
IonWarp never writes SGTM or LGTM. It reads each push against the code around it, posts what it finds, and leaves the approval to a person.
SGTM vs LGTM
Counts are from our sample of 12 open-source projects.[3]
| SGTM | LGTM | |
|---|---|---|
| Stands for | SGTM: Sounds good to me[1] | LGTM: Looks good to me[8] |
| Agrees with | SGTM: A plan, an answer, a suggestion | LGTM: The change itself: “what a code reviewer says when approving”[8] |
| Where you see it | SGTM: Issues, proposals, design docs, chat | LGTM: Pull request reviews |
| On GitHub | SGTM: A comment | LGTM: A comment; the Approve review is what counts[2] |
| On 1,129 merged pull requests | SGTM: 2 | LGTM: 265 |
Sources
- Wiktionary, SGTM, read 2026-11-18.
- GitHub Docs, Approving a pull request with required reviews, read 2026-11-18.
- IonWarp, Code review terms: how often they show up on 1,129 merged pull requests (counted 2026-11-10), read 2026-11-18.
- Go, Go Wiki: CodeReview, read 2026-11-18.
- Go on GitHub, Issue 78339: comment, read 2026-11-18.
- Go on GitHub, Issue 37561: comment, read 2026-11-18.
- GitHub Docs, Requesting a pull request review, read 2026-11-18.
- Google, Google Engineering Practices: Terminology, read 2026-11-18.
