Docs: add PR link check workflow DRAFT #25480
Draft
Conversation
This file contains hidden or 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
aimeeu
requested review from
a team and
mikegolus
and removed request for
a team
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
|
|
||
| - name: Get changed files in the content/tutorials/ subdirectories | ||
| id: changed-files | ||
| uses: tj-actions/changed-files@0874344d6ebbaa00a27da73276ae7162fadcaf69 # v44.3.0 |
Check warning
Code scanning / GitHub Actions Scanner
found OSV reported vulnerability in tj-actions/changed-files Warning
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.
Description
Both the tutorials repo and the new web-unified-docs repo have PR link check workflows. Because the web-unified-docs PR link check is part of the build preview workflow, I copied the tutorials workflow and modified a few spots.
I'll need a PR link checker in place when I implement the Nomad navigation refactoring. Not sure when Nomad docs will move to the web-unified-docs repo, so adding the PR link check workflow here.
I'm hoping Web Presence will weigh in with a review since they have much more experience with this type of workflow than I do.
Testing & Reproduction steps
?
Links
Jira: CE-840
Reviewer Checklist
backporting document.
in the majority of situations. The main exceptions are long-lived feature branches or merges where
history should be preserved.
within the public repository.