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
GitHub Availability Report: November 2024
In November, we experienced one incident that resulted in degraded performance across GitHub services.
The top 10 gifts for the developer in your life
Whether you’re hunting for the perfect gift for your significant other, the colleague you drew in the office gift exchange, or maybe (just maybe) even for yourself, we’ve got you covered with our top 10 gifts that any developer would love.
Congratulations to the winners of the 2024 Gaady Awards
The Gaady Awards are like the Emmy Awards for the field of digital accessibility. And, just like the Emmys, the Gaadys are a reason to celebrate! On November 21, GitHub was honored to roll out the red carpet for the accessibility community at our San Francisco headquarters.