-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use linkspector #9
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #9 +/- ##
=========================================
Coverage 100.00% 100.00%
=========================================
Files 2 2
Lines 7 7
=========================================
Hits 7 7 ☔ View full report in Codecov by Sentry. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM! Certainly good to have a more up-to-date (and maintained) version of this that works for all cases. Probably this now means we have to call this DevOps in every other repo, AFAIK we're just calling the old one everywhere, and not refer to this in DevOps...
Yeah, it is now clear that even if it wouldn't save much lines of code, it would still have been useful to refer to this workflow from the beginning. |
Use linkspector instead of markdown-link-check
markdown-link-check does not work with the new redirection scheme of SPIE, see AstarVienna/ScopeSim#322
The creator the github action we used to use, states that we should move to linkspector: https://github.com/gaurav-nelson/github-action-markdown-link-check
See #10 to see how the action looks for a broken link.