Add external links to docs#4
Conversation
make sure all links are valid by adding a link checker Co-authored-by: github-learning-lab[bot] <37936606+github-learning-lab[bot]@users.noreply.github.com>
|
Nice work! We've added a unit test to check for broken links. When a broken link was committed to our pull request, the test caught it and let us know the build had failed. Clicking on the Details link next to one of our statuses shows the following: Notice how the two stages build and testlinks both show as Travis CI jobs in our build. Also, notice that even though the Step 9: Fix the broken linkTo get our checks to pass, let's fix the broken link so both Travis CI checks are passing. You can click on the Details link next to the failed testlinks Travis CI test for more information. By doing so, you'll find the following error: ⌨️ Activity: Fix the broken link
I'll respond below with your next step. |
Co-authored-by: github-learning-lab[bot] <37936606+github-learning-lab[bot]@users.noreply.github.com>
|
Nice work! It might take a moment, but once both the build and testlinks tests are passing, it's time to merge this pull request. Step 10: Merge the unit test⌨️ Activity: Add the
|


With the addition of links to our code base, we should add a unit test as one of our Travis CI jobs that run whenever it builds. Let's add a test using HTMLProofer to test for any broken links, images, or HTML.
We'll now add the HTMLProofer test, but we'll also refactor some of the commands away from the config file into standalone test scripts.
Step 8: Apply batch suggested fixes to refactor config
Let's make sure all links are valid by adding a link checker unit test, and packaging into test scripts.
⌨️ Activity: Check for broken links using Travis CI
I'll respond below with your next step.