Allow the 6.7 docs to be rebuilt from this branch - #2636
Merged
Conversation
The 6.7 docs currently published are a build of master taken after the 6.8 release notes and bundled-Python install instructions had been merged there, so 6.7 serves 6.8 content. Rebuilding them has to happen from this branch, since the API reference and ShapeWorksCommands.md are generated from the binaries the workflow builds. Adds the workflow_dispatch inputs the deploy step needs and takes master's deploy_docs.sh, which builds the docs from the dispatched ref instead of unconditionally from master.
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
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.
The 6.7 docs on the site are a build of
mastertaken after the 6.8 release notes and bundled-Python install instructions had been merged there, so 6.7 serves 6.8 content — 26 files differ from thev6.7.0tag, includingusers/install.mdand the platform READMEs. Rebuilding them has to happen from this branch, since the API reference andShapeWorksCommands.mdare generated by running the binaries the workflow builds.The
v6.7.0tag cannot be used for this: it has noworkflow_dispatchtrigger, and itsdeploy_docs.shhardcodesgit checkout master, so dispatching there would republish master into 6.7 again. This adds the dispatch inputs the deploy step needs and takes master'sdeploy_docs.sh, which builds from the dispatched ref. Once merged, run Mac Arm64 Build on this branch withdeploy_docschecked anddocs_aliasset tolatest.