Link Checking Procedure

[rcomer]

📰 Custom Issue

Following the success of @jamesp’s GitHub Action Workflow to update conda lock files, the CI tests on contributors’ pull requests are protected from dependency updates and we can be fairly sure that any failures in the main tests are caused by the PR’s change. I think it would be great if, as far as possible, all CI failures in a PR were caused by that PR’s change.

Could we remove doc link checking from the PRs and have a regular GitHub Action to do it instead? It mostly fails because some external documentation has moved, so it doesn’t make sense to me that unrelated changes should be held up by it. I don’t really know anything about GitHub Actions, but this looks relevant: https://github.com/lycheeverse/lychee-action

[jamesp]

I'm all for this. I think PRs should be as atomic as possible

[jamesp]

We already have the configuration in cirrus ci, perhaps @bjlittle knows if it's possible to run cron-style jobs in cirrus? If not we could follow the template of the lockfile update github action

[bjlittle]

@jamesp Yup, you can run cron style jobs in cirrus-ci 👍

See https://cirrus-ci.org/guide/writing-tasks/#cron-builds

[github-actions[bot]]

In order to maintain a backlog of relevant issues, we automatically label them as stale after 500 days of inactivity.

If this issue is still important to you, then please comment on this issue and the stale label will be removed.

Otherwise this issue will be automatically closed in 28 days time.

[trexfeathers]

I really want to make this work 🤞