“Good first issue” is a label that maintainers attach to tasks in a code repository to mark them as approachable for someone who has never contributed before. It addresses a specific and common problem: a newcomer who wants to help a project often cannot tell which of dozens or hundreds of open issues is small, self-contained, and well-enough specified to be a reasonable first attempt. The label is a maintainer’s curated answer, a sign that says start here.
GitHub formalized the convention and built discovery features around it. The platform’s documentation advises maintainers to “apply the good first issue label to issues in your repository to highlight opportunities for people to contribute to your project,” and explains that GitHub “uses an algorithm to determine the most approachable issues in each repository and surface them in various places,” with the label increasing the likelihood that an issue is surfaced. Labeled issues also populate a repository’s dedicated contribute page, turning a manual tagging act into automatic visibility for the work.
The label travels with a companion, help wanted, and the two are not interchangeable. As the convention is generally understood and reflected in GitHub’s guidance, good first issue usually means a task has been curated specifically for newcomers, while help wanted signals that maintainers want outside help but the work may require more context or experience. Used together they let a project triage its backlog into a gentle on-ramp for beginners and a broader call for contributors who are ready for something larger.
The practice grew directly out of the open-source contribution model that the pull request made possible. Once anyone could fork a project, make a change, and propose it back without prior permission, the limiting factor shifted from access to orientation: the hardest part of contributing became knowing where to begin. Labels like good first issue are the social tooling that grew up to solve that orientation problem, and they pair naturally with other onboarding practices such as a welcoming README and seasonal events like Hacktoberfest that push newcomers toward their first contribution.
The effectiveness of the label depends entirely on maintainer discipline. A good first issue is only good if it is genuinely small, clearly described, and still unclaimed, and a project that mislabels difficult or stale work erodes the trust the label is supposed to create. At its best, though, the convention is a quiet but important piece of open-source culture: a low-cost, repeatable gesture by which an established project deliberately makes room for the next generation of contributors.