On Thu, Dec 17, 2020 at 05:40:31PM +0100, Christoph Berg wrote: > Re: Jelmer Vernooij > > It would be great if vcswatch could call a webhook whenever a packaging > > repository changed. > currently repository information is extracted from the Sources files > in unstable and experimental, i.e. vcswatch doesn't follow changes in > Vcs-* inside the repository. > > While in theory possible, it could mean that we'd have to chase a > non-trivial list of redirects if the other repository points elsewhere > as well. Not sure we'd want to go that route. > > Would the from-Sources-only repo information still be valuable for you > to have?
My bad, the word "changed" in my original bug was ambiguous. I'm interested in notifications when there are new commits to the packaging repository - rather than changes to the packaging repository URLs. > > This could be triggered whenever repositories are found to be different > > at poll time, but e.g. for salsa this could be triggered by a server side > > hook > > (https://docs.gitlab.com/ee/administration/server_hooks.html#create-a-global-server-hook-for-all-repositories) > I'm not sure I follow, do you want a general webhook in salsa that > would call out *to* vcswatch, or do you want a webhook *from* vcswatch > to elsewhere? I'm interested in a general webhook from vcswatch (or a something that provides similar functionality). For salsa repositories specifically, it may be possible to improve the reponsiveness of vcswatch by installing a server-side hook that notifies vcswatch whenever a salsa repository has changed.