-
Notifications
You must be signed in to change notification settings - Fork 125
gaurav-nelson/github-action-markdown-link-check is no longer maintained #439
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
Comments
If we want people to continue using markdown-link-check, I think we should provide our own github action. I don't know if linkspector is better or not / what's the differences |
Let's fork it. Makes sense for it to live with the other repositories I think. @tcort, please could you fork gaurav-nelson/github-action-markdown-link-check and add the rest of us as maintainers and I'll take it from there. |
Done! https://github.com/tcort/github-action-markdown-link-check |
I don't have any issues. I'll add the link to this action in |
@tcort Can I get access to the settings for the new repository to set up branch protection, default to squash merge etc.? |
I think I will want to detach the fork too, so that pull requests don't default to being made to @gaurav-nelson's repository. |
FYI: the new github action was tagged with 1.1.0 instead of v1.1.0, so the docs are broken (they say to use (I wrote this here, because issues are not enabled on the github action repo) |
Thanks @gjermundgaraba for checking the text and your recent PR. |
Good point @gjermundgaraba. I will do a new release. |
Done. Released as |
Uh oh!
There was an error while loading. Please reload this page.
@tcort @smainil @BaseMax
Options include:
Based on my initial tests the third one is not an option just yet, but it may be worth considering the benefits of joining forces on a single tool.
Thoughts?
The text was updated successfully, but these errors were encountered: