-
Notifications
You must be signed in to change notification settings - Fork 802
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
Run make linkcheck
in CI
#724
Comments
Absolutely agree. Thanks @minrk. |
Just did a make linkcheck. There are about 8 broken links and a number of redirects to new locations. I'm at Cal Poly today and will try to do a cleanup of the links and then add the linkcheck to Travis. |
ah this is a great idea |
❤️ |
If we run a linter, we should also start using black for Python code for style (over time). |
Ah deal @willingc I'll look into that! It is currently only linting yaml and verifying it makes sense with kubernetes resource specifications. |
Bumping this, I'd love to see this now that we are making additional changes to the docs. Looked at whats going on in the makefiles etc, but didn't quickly conclude what I needed to do. |
is this now just a matter of adding |
Hmmm, I think it will fail without proper reason due to "missing anchor" stuff that actually works though. If we make it Seems like we should check internal references rather than external, hmmm, perhaps make linkcheck also requires us to first do |
ah I see - perhaps something to just do as a "team process" kind of thing once in a while? Or is there a way to make the anchor links pass? |
@choldgraf I don't know - I did not investigate it though. |
Could you add a Travis cron job so you'll know if the master branch breaks? |
Sounds great @manics !!! |
We now have a linkcheck running that provide output on build, it has typically failed almost nonstop, but at the same time I've caught a lot of things thanks to it! Thanks @manics! |
There are quite a few broken links in our docs. We can and probably should be running
make linkcheck
in the docs as part of CI.cc @willingc
Related to #723
The text was updated successfully, but these errors were encountered: