search

opensourcepledge / opensourcepledge.com

We all depend on Open Source. Pay your share through Open Source Pledge.
https://opensourcepledge.com/
100 stars 15 forks source link

Add a slightly more comprehensive way of monitoring JSON files #113

Open vladh opened 1 week ago

vladh commented 1 week ago

What if a member's JSON file starts 404ing? Should they stop showing up on the website? Should they stay there, but with a warning label? Should we receive an alert, so that we can contact the member?

What if a member doesn't add an annual report for a long time? Should we receive an alert, so that we can ask them for one?

voxpelli commented 1 week ago

One flow I have started using is to use scheduled GitHub Actions to automatically raise PR:s with such changes.

Examples:

  1. https://github.com/SocketDev/socket-sdk-js/pull/228 (see workflow)
  2. https://github.com/neostandard/neostandard/pull/172 (see workflow)
  3. https://github.com/voxpelli/tsconfig/pull/59 (see workflow and especially this reusable one, which is the latest iteration of these three)

I could try to lend a hand in this if you are interested

vladh commented 6 days ago

Thanks @voxpelli! A workflow would be nice, but I think it needs to send an email or similar — if the JSON file is down on a member's website, we don't have the ability to fix that, so all we can do is let them know.