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.
Closes #35796
Only run the workflow on
pull_request
. It is not strictly necessary to run the workflow onmerge_group
, and doing so onpull_request
simplifies the branching logic we use in the workflow.Test the docs build using the
checkout
GitHub Actions workflow, rather than using the name of the branch. This way, we don't need custom logic to identify the branch name. To get this to work, turn thegit-update
script inpackage.json
into a no-op script. This will also make it easier to add the prose linting step toLint (Docs)
in the future, since we pull thegravitational/teleport
source outside of theyarn update-and-build
command.Combine the Vercel preview workflow and "test the docs build" step: Both of these run the docs build, so there is no need to separate the build step from the Vercel preview. This saves around 8-10 minutes of runner time per workflow run.