-
Notifications
You must be signed in to change notification settings - Fork 34
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
Add link checker to CI #145
Labels
Comments
dmethvin-gov
added
[type] enhancement
New feature or request
[practice] engineering
Engineering related work
labels
Jul 10, 2018
@dmethvin-gov Still a thing, or no? |
Yes, still a thing. If this takes quite a bit of time (it may if we scan all Markdown files) we'd only do this sporadically to avoid the extra work on every commit. |
dmethvin-gov
added a commit
to dmethvin-gov/us-forms-system
that referenced
this issue
Oct 2, 2018
Fixes usds#145 The link checking takes a long time when the file is big or there are many external links, so I'm only checking the markdown files actually changed in the commit.
dmethvin-gov
added a commit
to dmethvin-gov/us-forms-system
that referenced
this issue
Oct 2, 2018
Fixes usds#145 The link checking takes a long time when the file is big or there are many external links, so I'm only checking the markdown files actually changed in the commit.
dmethvin-gov
added a commit
to dmethvin-gov/us-forms-system
that referenced
this issue
Oct 2, 2018
Fixes usds#145 The link checking takes a long time when the file is big or there are many external links, so I'm only checking the markdown files actually changed in the commit.
9 tasks
dmethvin-gov
added a commit
that referenced
this issue
Oct 18, 2018
Fixes #145 The link checking takes a long time when the file is big or there are many external links, so I'm only checking the markdown files actually changed in the commit.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Per #143 I think we should be able to add https://github.com/tcort/markdown-link-check pretty easily. Rather than make it part of
npm run build
I'm inclined to just make it part of the CI for PRs and merges to master. When #97 is resolved we'll have a commit hook that runs build to ensure that all the built files are in sync with the source, and I'm concerned that checking all the links on each build would take too long.The text was updated successfully, but these errors were encountered: