feat: add file-no-broken-links rule #192
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…some bugs on linux
|
well crap. I borked this pretty good by pushing to the wrong remote, which merged these changes and closed the PR as merged :-\ I'll continue discussion of rollback (if you want that) in #194 |
Closed
|
🎉 This PR is included in version 0.10.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hello! I'm back again with another largish PR.
This PR adds support for checking markup files for broken links using the
file-no-broken-linksrule. This rule is meant to help catch those times when linked file/website in the README got deleted, and the link was never updated. To quote the rules documentation:In addition to adding this rule, I reworked the Dockerfile and Github Actions workflows to reflect the new dependency on github-markup, and updated both the npm and ruby dependencies to newer versions. None of my changes should break existing repolinter setups.
Since the dependency list for a fully-functional repolinter installation is now rather long, my next item of business is reworking repolinter-action to support licensee, linguist, and github-markup.