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
Developers still need the right to challenge junk patents
Calling on developers, startups, and open source organizations to advocate against patent rules that would make it harder to challenge bad patents by the December 2 deadline.
GitHub Availability Report: October 2025
In October, we experienced four incidents that resulted in degraded performance across GitHub services.
TypeScript, Python, and the AI feedback loop changing software development
An interview with the leader of GitHub Next, Idan Gazit, on TypeScript, Python, and what comes next.