docs: update staging deployment flow #173
Merged
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
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 updates the docs to show how the staging deployments for this site now work. See this comparison for the changes to CI.
Notable changes:
pull_request_targetis included in the mainpublish.ymlworkflow. That event controls which ref is checked out and whether the deploy job is a preview or not.mainis explicitly checked out. This allows us to push commits when fetching/updating the CLI docs, and then the call thepublish.ymlas a reusable workflow but still have it deploy the latest.stage-pull-request.ymlhas been removed and all deployments (production and preview) occur in this repoThese changes are already in use, but I will leave this PR open for visibility and discussion.
/cc @MylesBorins