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
An update on GitHub availability
Here’s what we’ve done—and what we’re still doing—to improve our availability and reliability.
GitHub Copilot is moving to usage-based billing
Starting June 1, your Copilot usage will consume GitHub AI Credits.
Changes to GitHub Copilot Individual plans
We’re making these changes to ensure a reliable and predictable experience for existing customers.