Skip external link check during CI on main branch
#848
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
This commit splits building and testing external links into two separate actions, and skips the link checker for builds on the main branch. This ensures that the main branch is always in a deployable state, even if it contains broken links.
robinjam
force-pushed
the
skip-link-checks-on-main
branch
from
706f616
to
5a7b43f
Compare
robinjam
changed the title
main branchmain branch
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.
This commit splits building and testing external links into two separate actions, and skips the link checker for builds on the main branch.
This ensures that the main branch is always in a deployable state, even if it contains broken links (for example, if it contains new files that have self-referential links within them, as is the state of this repo right now).
Note that CI is expected to fail for this PR. The issue should go away after the next successful deploy, in the meantime we will need to merge this PR bypassing the status check.