Dear GitHub, I’ve just arrived #2
Decoding Open Source Slang: What Do “Good First Issue”, “LGTM”, and Other Terms Really Mean?

Dear GitHub, I’ve just arrived #2
Decoding Open Source Slang: What Do “Good First Issue”, “LGTM”, and Other Terms Really Mean?
If you’ve ever scrolled through a GitHub repo and wondered whether “LGTM” is a new programming language or if “good first issue” is code for a hidden Easter egg? you’re not alone.
When I first started exploring open source, I was excited to contribute but completely lost in the sea of unfamiliar terms like “good first issue,” “LGTM,” and “WIP.” I had no idea what they meant, and it felt like reading a secret developer language.
Welcome to the lingo jungle of open source — a world where slang isn’t just fun, it’s functional. Whether you’re a budding contributor, a curious lurker, or an experienced dev brushing up your vocab, this blog breaks down popular open source slangs, their meanings, and how to use them. Learn with me.
What Is Open Source Slang, Anyway?
Open source communities thrive on collaboration and that means fast communication. Instead of writing long sentences, developers use shorthand and slang to keep things snappy, especially in issues, PRs (pull requests), and reviews.
These terms aren’t just cute they’re useful labels that help filter, prioritize, and simplify discussions.
Popular Open Source Slangs You Should Know
1. Good First Issue
What it means: This tag highlights issues that are ideal for beginners. These tasks are generally low-risk, well-documented, and serve as your entry ticket into a project.
Use it when: You’re new to open source and want a confidence-boosting task that won’t wreck production.
“Hey, I’m new here! I saw this issue marked as
good first issuemind if I take it up?"
SEO Tip: Searching for good first issue GitHub is a great way to find beginner-friendly contributions.
2. LGTM — Looks Good To Me
What it means: A reviewer uses this to approve your pull request. It’s their digital thumbs-up.
Use it when: You’re reviewing a PR and don’t see any issues.
“Code is clean and tests are passing LGTM!”
Fun fact: Some repos even use bots to merge PRs once enough “LGTM” comments are received.
3. PR — Pull Request
What it means: A pull request is how you submit your code changes to a project. Think of it as a “Hey, here’s my work can someone review it?”
Use it when: You’re ready to contribute and want feedback or approval.
“I’ve pushed a fix for the bug we discussed PR incoming!”
4. Issue
What it means: A way to track bugs, enhancements, or questions in a repository.
Use it when: You’ve found a bug, need help, or want to suggest a feature.
“Opening an issue to track the dropdown bug in the navbar.”
5. Thread / Threaded Discussion
What it means: A chain of comments under an issue or PR like mini-forums.
Use it when: You want to keep conversations organized around specific parts of the discussion.
“Let’s move this conversation to a new thread under the design proposal.”
6. Chore
What it means: A task that’s necessary but doesn’t add direct value to the user (e.g., updating dependencies, renaming files).
Use it when: You’re making cleanup changes.
“Pushed a chore PR to remove unused imports across the codebase.”
7. WIP — Work In Progress
What it means: A PR or issue that isn’t ready for review or merge yet.
Use it when: You want to share early work and get feedback.
“Heads up this PR is WIP, but feedback is welcome!”
8. NIT — Nitpick
What it means: A very minor comment or suggestion, often about formatting or naming.
Use it when: You don’t want to block a PR but want to mention something small.
“NIT: consider renaming this variable for clarity.”
9. Ping
What it means: A gentle nudge for attention or action.
Use it when: A PR or issue hasn’t received a response in a while.
“Just pinging to check if there’s any update on this PR!”
10. Stale
What it means: An issue or PR that hasn’t seen activity in a while.
Use it when: You’re cleaning up inactive tasks, or trying to revive one.
“Marking this PR as stale feel free to reopen if needed!”
Mastering open source slang not only helps you communicate better but also makes contributing smoother, smarter, and a lot more fun.
메타데이터
- post_id
- 5dec429dd857
- slug
- dear-github-ive-just-arrived-2-5dec429dd857
- url
- https://medium.com/@varshy/dear-github-ive-just-arrived-2-5dec429dd857
- canonical_url
- https://medium.com/@varshy/dear-github-ive-just-arrived-2-5dec429dd857
- author_url
- https://medium.com/@varshy
- status
- ok
- fetched_at
- 2026-07-18 12:57:10