Hi,
Right, this is cool. The problem is that the upstream repo would
need
to be configured to provide a public message that something has been
changed
in it (i.e. new release) so the question is how to do this part.
Ah, right, setting up a webhook needs access to the upstream repo too.
Add support for polling then? Possibly at large intervals only to cap
the resources spent on this? Maybe once per day, so one could do
nightly builds with this?
cheers,
Gerd