HelloGitHub is entirely powered by community contributions. Anyone — regardless of experience level, nationality, or background — can recommend a project for inclusion in an upcoming issue. You can submit a project you discovered and found inspiring, or even self-nominate your own open-source work. Submissions are made through GitHub Issues on the HelloGitHub repository, and accepted projects are credited to the contributor by GitHub username. With 458+ contributors already listed, the door is always open for the next one.Documentation Index
Fetch the complete documentation index at: https://mintlify.com/521xueweihan/HelloGitHub/llms.txt
Use this file to discover all available pages before exploring further.
Submission Requirements
Follow these steps to submit a project for consideration in a future HelloGitHub issue.Find a project
Identify an open-source project hosted on GitHub that you believe is interesting, beginner-friendly, or otherwise noteworthy. The project must have a public GitHub repository. Projects hosted on other platforms (GitLab, Bitbucket, etc.) are not eligible.
Check for duplicates
Before submitting, visit hellogithub.com and use the search feature to confirm the project has not already been featured in a previous issue. Duplicate submissions are automatically declined, so this step saves everyone time.
Open a GitHub Issue
Navigate to the HelloGitHub repository Issues page and click New Issue. Select the “Submit Project” template to load the pre-formatted submission form.
Fill in the form
Complete all required fields in the submission template. See the Submission Form Fields section below for a detailed breakdown of each field, including character limits and formatting expectations. Incomplete or poorly filled submissions are less likely to be accepted.
Wait for review
The HelloGitHub editorial team will review your submission. If it is accepted, your GitHub username will be added to the contributors list and you will receive a notification in the original issue thread. If it is not accepted, the team may leave feedback explaining why.
Submission Form Fields
Each submission uses a structured form. The table below describes every field, its requirements, and guidance on how to fill it in effectively.| Field | Required | Constraints | Guidance |
|---|---|---|---|
| Project URL | ✅ Yes | GitHub repository URL only | Must be a direct link to the GitHub repo (e.g. https://github.com/owner/repo). No links to forks, mirrors, or external sites. |
| Category | ✅ Yes | See options below | Choose the programming language or category that best describes the project. |
| Project Title | ✅ Yes | Max 50 characters, ~20 words | A concise headline summarizing the project. Think of it as the one-sentence pitch a reader sees before deciding to learn more. |
| Project Description | ✅ Yes | 32–256 characters | Describe what the project does, its key features, practical use cases, and what a beginner would learn from it. Do not copy the project’s own README description verbatim. |
| Highlights | ✅ Yes | Free text | Explain what makes this project stand out compared to similar tools or alternatives. What is unique, surprising, or especially well-done about it? |
| Example Code | Optional | Markdown code block | If the project is a library or CLI tool, include a short, representative code snippet that shows it in action. |
| Screenshots / Demo | Optional | Image or video URLs | Link to screenshots, GIFs, or video demos that visually communicate what the project does. |
Tips for Acceptance
Following a few best practices will significantly increase the chance that your submission is accepted and included in an upcoming issue.- Write original descriptions. Do not copy the project’s own README or GitHub description word-for-word. The HelloGitHub editorial team writes in its own voice, and submissions that feel like copy-pastes are typically rejected or heavily edited.
- Read the review guidelines. The Project Review Guidelines explain in detail what the editorial team looks for. Familiarise yourself with them before submitting.
- Tailor your submission to the guidelines. The description and highlights fields should directly address the review criteria: is it beginner-friendly? Is it interesting? Is it actively maintained? Answer those questions in your own words.
- Submit projects with good documentation. A project with no README, no examples, and no documentation is hard to recommend to beginners. Well-documented projects are far more likely to be accepted.
- One project per issue submission. Open a separate GitHub Issue for each project you want to recommend. Do not bundle multiple projects into a single submission.
Contributor Recognition
Every accepted submission is a permanent contribution to HelloGitHub. Contributors who have had projects accepted are listed by GitHub username in the contributors file, which is publicly accessible in the repository. Contributors who reach the milestone of 10 or more accepted projects are recognized as core contributors — a distinction that reflects sustained, meaningful participation in the HelloGitHub community.Currently HelloGitHub has 458+ contributors listed in the contributors file.
View Contributors
Browse the full list of community contributors who have had projects accepted in HelloGitHub issues.
Submission Guidelines
Read the detailed project review guidelines to understand exactly what the editorial team looks for in a submission.