It would be helpful to have a run-link-check label which can be added to PRs, similarly to how the run-benchmark label works, to ensure link-check succeeds without needing to find workarounds to actually get the link-check to test to run.
Recent examples of where this would have helped to save time:
Perhaps a corresponding checklist item should also be added to the default PR form under the "Documentation" section, something like:
- [ ] If this PR updated any links in any `.rst` files, ran `link-check` to test for broken links.
<!-- Adding the run-link-check label (if your uxarray repo permissions allow it) will run link-check
If you need link-check to be run but don't have permissions, leave this item unchecked for now. -->
It would be helpful to have a run-link-check label which can be added to PRs, similarly to how the run-benchmark label works, to ensure link-check succeeds without needing to find workarounds to actually get the link-check to test to run.
Recent examples of where this would have helped to save time:
mainwithout ever running link-check, which led to broken links that needed to be debugged as part of 1675 (but not as the originally-noticed main cause of 1675).Perhaps a corresponding checklist item should also be added to the default PR form under the "Documentation" section, something like: