6 ms·

Unfortunately, there is no RSS/Atom feed for issues or pull requests. I made a little Ruby script (https://github.com/bhaak/github-feeds https://github.com/bha

by bhaak 7y ago

Unfortunately, there is no RSS/Atom feed for issues or pull requests. I made a little Ruby script (https://github.com/bhaak/github-feeds https://github.com/bhaak/github-feeds) that outputs static RSS files but you would expect that GitHub would have exported those by themselves.

captn3m0 7y ago
You can also use RSS-Bridge[1], which covers GitHub Feeds, and lot more sites. My instance[0] has the GitHub bridges enabled, and I subscribe to a few issues on our Slack channels this way. [1]: https://github.com/RSS-Bridge/rss-bridge https://github.com/RSS-Bridge/rss-bridge [0]: https://rss-bridge.bb8.fun/ https://rss-bridge.bb8.fun/ I like your static-file approach though. Never thought of pre-generating RSS-feeds that way.
- bhaak 7y ago
  Yes, it's certainly not a very generic solution but it was my special itch to scratch. These days, I don't have much patience trying to find a solution for something the content provider should have done by themselves and installing a large program to do it which then might not even scratch my itch exactly like I want it to ... yeah, I rather invest an hour or two and come up with a simple solution of which I at least understand the limitations. Static files are bliss. They might not be up to date to the millisecond but you will never have a problem pulling them or otherwise your whole service is going down in flames anyway. If you do need real time updates, you wouldn't use RSS anyway, so this is a very workable compromise.
pcr910303 7y ago
> I made a little Ruby script (https://github.com/bhaak/github-feeds https://github.com/bhaak/github-feeds) that outputs static RSS files but you would expect that GitHub would have exported those by themselves. Hmm, that looks likes exactly the target use case for GitHub Actions... running the static export script on every issue/PR would work well. My next weekend project seems to be this... :-)

by bhaak 7y ago

captn3m0 7y ago

You can also use RSS-Bridge[1], which covers GitHub Feeds, and lot more sites. My instance[0] has the GitHub bridges enabled, and I subscribe to a few issues on our Slack channels this way. [1]: https://github.com/RSS-Bridge/rss-bridge https://github.com/RSS-Bridge/rss-bridge [0]: https://rss-bridge.bb8.fun/ https://rss-bridge.bb8.fun/ I like your static-file approach though. Never thought of pre-generating RSS-feeds that way.

bhaak 7y ago
Yes, it's certainly not a very generic solution but it was my special itch to scratch. These days, I don't have much patience trying to find a solution for something the content provider should have done by themselves and installing a large program to do it which then might not even scratch my itch exactly like I want it to ... yeah, I rather invest an hour or two and come up with a simple solution of which I at least understand the limitations. Static files are bliss. They might not be up to date to the millisecond but you will never have a problem pulling them or otherwise your whole service is going down in flames anyway. If you do need real time updates, you wouldn't use RSS anyway, so this is a very workable compromise.

pcr910303 7y ago

> I made a little Ruby script (https://github.com/bhaak/github-feeds https://github.com/bhaak/github-feeds) that outputs static RSS files but you would expect that GitHub would have exported those by themselves. Hmm, that looks likes exactly the target use case for GitHub Actions... running the static export script on every issue/PR would work well. My next weekend project seems to be this... :-)