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.
Doesn’t work with Google Reader.
First, the link in the feed icon points to the https URL, which redirects to http. Maybe the icon should point to http in the first place? You never know how readers handle redirects, especially when they’re 302, not 301.
I can get the http feed with curl, and feed validator also seems to be able to fetch it (although it doesn’t validate, at least it sees it as a proper feed). But Reader still errors out on that URL saying that there is “no feed available on …”. Lame
The feed has been verified to work in Google Reader by more than one person. If you’re having trouble with it, please drop in #github sometime and we can help you out. Also, try adding a bogus parameter to the querystring like ?token=secrettoken&blah=blah. This may force Google Reader to not used its cached version.
Is it possible to have something like this but for “Repository -> Network -> Feed” feed?
+1 for private token feeds per repository