It would be beneficial to implement a CI job that verifies our compliance with SPEC-0 and adds a badge to indicate the current status: scientific-python/specs#240.
This job should run daily or weekly, rather than only on merge, as prolonged periods without code changes could result in us falling outside the SPEC-0 timeline. Consequently, the badge should turn red.
CC @ajkswamy
It would be beneficial to implement a CI job that verifies our compliance with SPEC-0 and adds a badge to indicate the current status: scientific-python/specs#240.
This job should run daily or weekly, rather than only on merge, as prolonged periods without code changes could result in us falling outside the SPEC-0 timeline. Consequently, the badge should turn red.
CC @ajkswamy