Make the repository visible
Keep the repository public, active, and easy to evaluate from GitHub without private context.
For maintainers
For maintainers
Help Good First Issue discover, evaluate, and keep beginner-friendly work in your repository useful for new contributors.
Discovery
Get your repository indexed
Good First Issue currently indexes public GitHub repositories and open GitHub issues. There is no self-serve submission form yet, so the strongest signal is a public repository that is easy to evaluate and maintain.
Document the project basics
Keep the README, CONTRIBUTING guide, license, local setup, and test instructions clear enough for a new contributor to follow.
Ask for indexing help
Leave beginner-friendly issues open when they are still valid, and use GitHub Discussions or the contact page to request indexing feedback.
Issue labels
Label beginner-friendly issues
The current fetch task searches GitHub for open issues with good first issue and help wanted labels. Those labels make your work easier to discover, but the issue still needs enough context for a first-time contributor to act safely.
Include enough context to make the first pull request reviewable
- Background for why the issue matters.
- Expected outcome in concrete terms.
- Files, packages, or product areas to inspect first.
- Test commands or manual verification steps.
- Whether contributors should confirm scope before coding.
Recommendations
Improve recommendation quality
Recommendations work best when the repository shows active maintenance and the issue is small enough for a new contributor to finish without guessing project direction.
Recent maintenance
Recent commits, replies, and triage activity help contributors trust that review is still possible.
Clear issue writing
Issues with context, acceptance criteria, and setup notes are easier to match with new contributors.
Small reviewable scope
Low-risk documentation, tests, UI polish, and small bug fixes are easier to recommend than broad design work.
Healthy contributor loop
Runnable tests and responsive feedback reduce abandoned pull requests and keep recommendations useful.
Avoid issues that look beginner-friendly but are hard to finish
- Stale issues that no maintainer has confirmed recently.
- Large features with unclear ownership or product direction.
- Tasks that require private context, credentials, or release access.
- Issues without reproduction notes, setup guidance, or expected behavior.
Need a repository reviewed?
Share the repository, the labels you use, and any feedback about how your issues appear on Good First Issue.