Token Private Feeds
Apparently some of the more popular feed readers can’t handle HTTP authentication, SSL feeds, or a combination of the two. No matter! GitHub private feeds are now accessible via a…
Apparently some of the more popular feed readers can’t handle HTTP authentication, SSL feeds, or a combination of the two. No matter! GitHub private feeds are now accessible via a private token.
Note that whenever you change your password, your token will change. This is a feature – if you’re ever worried about your token getting out there, just change your password.
The old, HTTP authenticated feeds still work without a token, too.
Update: Thanks to Mislav, the feed now validates (whoops) and works over SSL.
Written by
Related posts
The next developer interface is ambient intelligence
AI, agents, voice, and physical controls are shifting software development from operating tools to expressing intent—and helping developers stay focused on building.
GitHub availability report: September 2026
In September, we experienced two incidents that resulted in degraded performance across GitHub services.
10 technical talks I’m excited about at GitHub Universe 2026
From verifying AI-written code to securing npm dependencies, these are the sessions I’m building my Universe agenda around.