Thomas Perl

@vimagick Needs rebasing, and there's still the two items from above. Thanks!

Closing after no activity. Feel free to reopen and update the PR.

Right now, reporter-related configuration per job isn't possible. You have to rely on having multiple configurations and/or set up mailing lists or something. Because reports are grouped (so there's only...

> > Because reports are grouped > > Trying to rebase before PRing, I discover the existence of new option "separate", > > https://github.com/thp/urlwatch/blob/e342af925930114b4194f1bdb660dec6348f653a/lib/urlwatch/reporters.py#L130 > > Can this be used...

The best way would be to use some template language outside of urlwatch and then let it generate the urls.yaml file from that template. This sounds like a very involved...

It depends on what the server does, e.g. maybe it checks user-agent or some other headers (it's probably not your IP address if `wget` works). You can override the user-agent...

In general, it's a good idea. And as long as the existing format is still supported, that shouldn't affect existing users. Not too happy with "reporters" below "report". We could...

Great, I like the compromise (backwards compatible) variant better, because it means less disruption for existing users. And maybe you can split the possible PRs into two, once that adds...

> WIP on this, for after tags are merged in: https://github.com/thp/urlwatch/compare/master...Jamstah:multiple-reporters?expand=1 Tags is now merged if you want to tackle this, too.

You mean the docs on https://urlwatch.readthedocs.io/en/latest/ or the ones that one can build locally?