r/github rules, stats, and what to post
Know the rules before you post. So easy grandma can do it.
- To post
- No minimum in the rules
- To comment
- No minimum in the rules
- Self-promotion
- Banned
- Links
- Not mentioned in the rules
- Promo risk
- High
- From the rules, not from removal counts
- Community age
- 16 years
- Since Oct 2010
- Flair
- Required on every post
About r/github
A source-backed Rankhog guide to r/github: public rules, community context, posting fit, and startup-promotion risk before you publish.Checked from the r/github rules on Reddit.
r/github rules
8 rules, in the community's own words.
- 1
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.
- 2
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
- 3
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.
- 4
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.
- 5
Use appropriate flairs
Posts without proper flair may be removed (doesn't apply to posts that don't fit any of the existing flairs).
- 6
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.
- 7
Be respectful and follow Reddiquette
No rude behavior, trolling, pointless complaining, spam, or promoting scams.
- 8
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.
What to post in r/github
What fits the room, and what gets removed.
Works well
- A detailed technical breakdown of a new feature released on the GitHub platform.
- A thoughtful discussion about how GitHub products can solve a specific industry problem.
- Sharing a technical insight about the functionality of GitHub's ecosystem.
- A post analyzing the differences between various GitHub products.
Avoid
- Posting just a URL or contribution charts without any real context.
- Asking for help with writing, fixing, or understanding code.
- Promoting your project in any thread that is not the dedicated pinned megathread.
- Posting content that is disrespectful, spammy, or trolling.
- Submitting content that is not clearly related to GitHub's platform or features.
Best hours to post in r/github
No pattern yet. r/github does not have enough top posts from the last 90 days to name its best hours.
What r/github Is For
This subreddit is a place to discuss GitHub's platform, products, and features. It is not the place to ask about projects that are hosted on GitHub. It also directs people to r/git if they have questions related to Git.
Rules That Matter Before Posting
The rules that will decide if your marketing adjacent post survives are “Content must be on-topic”, “No low-effort posts”, “No coding or Git help requests”, “Promote your projects in the pinned megathread”, “Use appropriate flairs”, and “Post must be in English”.
What To Post
A good post here should offer thoughtful context or technical insights about GitHub. You should discuss GitHub's platform or features in a meaningful way, rather than just linking a repository. Always make sure your post has an appropriate flair and that the title is in English.
What To Avoid
You should avoid submitting content that is low effort, like just posting a URL or a contribution chart. You must also avoid asking for coding help, as those questions belong in places like r/learnprogramming or StackOverflow. Finally, you must avoid self-promotion anywhere except the pinned megathread.
A note from Anthony
It is very clear that this community is extremely strict about self-promotion, which is a huge thing to remember. The rules make it very easy to get removed if you try to promote outside of the designated megathread. I think the focus here is purely on technical discussion about the platform itself.
By Anthony Riera, founder and operator of Rankhog. Every guide is built from the community's own public rules and data, then checked by Rankhog's grounding audit before it goes live.
Common questions about r/github
What subreddits are similar to r/github?
Subreddits like r/github are r/programming, r/ProgrammerHumor, r/learnprogramming, r/webdev, r/mac, r/AskEngineers, r/javascript and r/gamedev.
Should I ask a Git question here instead of going to r/git?
If you are asking about Git itself, you need to go to r/git, because this subreddit is specifically for GitHub's platform and products.
Where is the correct place to share my personal project?
You must share your projects only in the dedicated megathread that is pinned at the top of the subreddit.
What are the basic requirements for posting successfully here?
Your post must have a proper flair, and the title of your post needs to be in English.
Subreddits like r/github
Other rooms for the same crowd.