Can I share my project as its own post?
No, the rule says self-promotion and project sharing should only happen in the dedicated pinned megathread.
Subreddit guides
r/github rules, stats, and what to post
A source-backed Rankhog guide to r/github: public rules, community context, posting fit, and startup-promotion risk before you publish.
By Anthony Riera, founder and operator of Rankhog.
Subreddit guides combine public Reddit source URLs, captured rules, visible verification dates, and Rankhog's account-safety workflow.
Current public stats
- Members
- 212,973
- Verified
- September 18, 2026
- Category
- Technical product and developer communities
Rules can change, so Rankhog keeps verification dates and the original public Reddit sources visible.
Rule summary
- Content must be on-topic: All posts must clearly relate to GitHub, including thoughtful context, technical insights, or meaningful discussion. Simply linking a repository is not sufficient.
- No low-effort posts: Avoid submitting content lacking effort. Examples include posting just a URL, contribution charts, promoting profiles, complaints about captchas or questions that can easily be Googled or answered before
- No coding or Git help requests: Posts asking for help with writing, fixing, or understanding code should be directed to more appropriate communities like r/learnprogramming or StackOverflow. Keep discussions focused on GitHub itself.
- Promote your projects in the pinned megathread: To keep the subreddit clean and focused, self-promotion and project sharing should only happen in the dedicated megathread pinned at the top.
- Use appropriate flairs: Posts without proper flair may be removed (doesn't apply to posts that don't fit any of the existing flairs).
- Post must be in English: Post titles must be in English. Non-English content in the body is allowed if an English translation is included.
- Be respectful and follow Reddiquette: No rude behavior, trolling, pointless complaining, spam, or promoting scams.
- Account suspension posts: Complaints about your account being suspended or shadowbanned should be added to the pinned post. Any other posts on this subject will be removed.
Works well
- A standalone post explaining a non-obvious behavior of a GitHub feature, with technical context and the correct flair.
- A discussion about a recent GitHub product change or limitation, written to invite meaningful input from other users.
- A short, honest project share inside the pinned megathread, with a one-line description and a link to the repository.
- A post comparing GitHub workflows or settings, focused on how the platform handles the problem rather than on your own tool.
Avoid
- Posting a bare link to your repository without any context or discussion, since the rule says simply linking a repository is not sufficient.
- Sharing your project or doing self-promotion anywhere outside the pinned megathread.
- Asking for help writing, fixing, or understanding code, which belongs in r/learnprogramming or StackOverflow instead.
- Posting about your account being suspended or shadowbanned outside the pinned post on that subject.
- Submitting without a flair when one of the existing flairs fits your post.
- Posting a title in a language other than English, since post titles must be in English.
What r/github Is For
This community is for discussing GitHub as a platform, including its products and features. It is not for questions about projects that are hosted on GitHub, and it is not for Git questions, since the description points people to r/git for that. The room is focused on GitHub itself, so the people posting here are users, developers, and teams who want to talk about how GitHub works, what changes, and what could be better.
Rules That Matter Before Posting
The rule named Content must be on-topic decides whether your post survives, because it says all posts must clearly relate to GitHub and that simply linking a repository is not sufficient. The rule named No low-effort posts matters too, since it removes posts that are just a URL, a contribution chart, or a profile promotion. The rule named No coding or Git help requests keeps the room focused on GitHub itself. The rule named Promote your projects in the pinned megathread is the one that controls all self-promotion. The rule named Use appropriate flairs means a post without a flair can be removed. The rule named Account suspension posts sends suspension complaints to the pinned post. The rule named Post must be in English applies to titles. The rule named Be respectful and follow Reddiquette covers rude behavior, spam, and scams.
What To Post
A good post here is a real discussion about GitHub the platform, not a project pitch. If you are a founder, the safest path is to put any project share inside the pinned megathread and keep it short. If you want a standalone post, write something that adds technical insight about a GitHub feature, a workflow, or a change you noticed. Give thoughtful context so the post clearly relates to GitHub. Pick the right flair before you submit. Write your title in English. If you mention your own product, tie it to a GitHub feature or use case rather than making the product the whole point.
What To Avoid
Avoid posting just a URL or a repository link with no context, because that is called out as low effort and as not sufficient. Avoid any self-promotion or project sharing outside the pinned megathread. Do not ask for help writing, fixing, or understanding code. Do not post about your account being suspended or shadowbanned outside the pinned post for that topic. Do not post without a flair if one fits. Do not post a title in a non-English language. Do not be rude, troll, spam, or promote scams.
Use Rankhog before posting in r/github
Want the version that does not run out? Subscribers get unlimited tool runs and more careful checks before posting.
Get my free Reddit SEO auditStart your 3-day free trial. Card required. $99/month after trial. Next, connect a verified Reddit account; no strategy starts until you explicitly start Rankhog.
Common questions about r/github
Can I just link my repository in a post?
No, because simply linking a repository is not sufficient. You need thoughtful context, technical insights, or meaningful discussion about GitHub itself.
Can I ask for coding or Git help here?
No, those posts should go to r/learnprogramming or StackOverflow. This subreddit is focused on GitHub itself.
Can I post about my GitHub account being suspended?
No, those complaints should be added to the pinned post, and any other posts on the subject will be removed.
Do I need to use a flair?
Posts without proper flair may be removed, unless none of the existing flairs fit your post.
Related subreddit guides
r/technology
Technical product and developer communities
A source-backed Rankhog guide to r/technology: public rules, community context, posting fit, and startup-promotion risk before you publish.
- Members
- 20.5M
- Verified
- 2026-09-18
r/programming
Technical product and developer communities
A source-backed Rankhog guide to r/programming: public rules, community context, posting fit, and startup-promotion risk before you publish.
- Members
- 6.9M
- Verified
- 2026-09-18
r/learnprogramming
Technical product and developer communities
A source-backed Rankhog guide to r/learnprogramming: public rules, community context, posting fit, and startup-promotion risk before you publish.
- Members
- 4.4M
- Verified
- 2026-09-18