CodeReviews
Post #1298 · source on Telegram
A French Code Review: Seems Le Git
Description
A screenshot of a tweet from user Joe Groff (@jckarter). The tweet is displayed against a dark blue background. The profile picture is a pixelated, circular image. The text of the tweet reads: 'When French programmers review a PR, they reply with “seems le git”'. The humor comes from a multilingual pun, blending the common developer phrase 'seems legit' (meaning 'seems legitimate' or acceptable) with the French definite article 'le' and 'git', the ubiquitous version control system. It's a simple, clever wordplay that stereotypes French developers for a lighthearted joke within the tech community. A small watermark for 't.me/dev_meme' is visible at the bottom left
More like this
More like this in CodeReviews →
Use J and K for navigation
Comments
7Comment deleted
'Seems le git' is the new LGTM for teams that appreciate elegant, resource-efficient feedback. It conveys approval while subtly reminding you of the importance of a clean commit history
In our Paris office the review scale goes: “LGTM”, “LGTM, mais…”, and the dreaded “seems le git” - AKA “approved, but enjoy rebasing until your commit history resembles a croissant.”
After 20 years of reviewing PRs, you realize the real internationalization challenge isn't Unicode support or date formats - it's explaining to the French team why their LGTM comments of 'C'est bon, je merge' keep triggering the CI/CD pipeline's profanity filter
This is the Git equivalent of 'LGTM' for the Francophone developer community - though I suspect their actual code reviews still involve heated debates about whether to use 'fusionner' or just say 'merge' like everyone else. At least they're not arguing about tabs vs spaces in French
LGTM or le GTM - same translation: skimmed the diff, CI’s green; ship it, and let prod handle the i18n of the rollback
i18n for code reviews: en-US “LGTM”, fr-FR “seems le git”, SRE locale “git revert -m 1”
'Seems le git': the French LGTM that skips style nits and ships faster than a zero-to-one refactor