This topic was automatically generated from Slack. You can find the original thread here.
Gabriel Bassinello : The trigger Github > New Release (instant) have to be on one of my github repositories? Can’t I point this trigger into a public repository to get notified when there’s a new release?
Dylan Sather (Pipedream) : this is actually a limitation of the GitHub API. You can’t create webhook notifications for a repo you don’t have write access to (the instant trigger works by creating a webhook in the repo that points to Pipedream).
If you’re interested, you can use the octokit npm package to poll a public for new releases and send yourself a notification when a new release shows up.
The “Pipedream way” to do this would be to author your own event source that runs on a schedule, polling the repo for new releases, and emitting an event when you find a new release. You can find a few similar examples in our repo (e.g. Hacker News, UserVoice, etc.)
You can also accomplish the same thing by running a workflow with a Cron Scheduler trigger, polling GitHub and keeping track of the most recent release using workflow state. Each time the workflow runs, you can compare the newest release against the release ID you have stored in state, and notify yourself only when there’s a new release.
Let me know if that helps!
Gabriel Bassinello : I managed to get this working using Github’ public RSS feeds.
Every repo has a public atom file like this (Release notes from tflint)
I created a RSS Feed source that runs every 12 hours and polls the latest release. If the last entry is different than the previous, run the workflow.
Thanks for showing different ways to do this Dylan, octokit is very interesting as well.
Dylan Sather (Pipedream) : Oh nice, I forgot they had public RSS feeds - great solution and much easier!
Gabriel Bassinello : Dylan, check out the result in share-your-work, i’m proud of it!
Dylan Sather (Pipedream) : I just saw - very cool! Quite robust
Gabriel Bassinello : I enjoyed the process, thank you for the help!