Repository navigation
Fix docs deploy output path and add manual branch dispatch - #615
Merged
Merged
Conversation
Copilot
AI
changed the title
[WIP] Fix deployment workflow and output path for docs
Fix docs deploy output path and add manual branch dispatch
Jul 28, 2026
mike-parkhill
approved these changes
Jul 28, 2026
mike-parkhill
marked this pull request as ready for review
July 28, 2026 20:17
maycon-mello
approved these changes
Jul 28, 2026
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 docs deploy workflow currently builds mdBook output outside the repository root, while deploy still publishes
out/, which leaves/sdk/outmissing at deploy time. This updates mdBook to write into repo-localout/and adds manual dispatch so maintainers can validate the workflow on a branch before merge.Build output path
mdbookscript to emit tutorials intoout/tutorialsunder the repository root.FOLDER: out, so the workflow publishes the same top-level docs directory structure without relying on..path traversal.Workflow trigger
workflow_dispatchto.github/workflows/docs.ymlin addition to the existingpushtrigger onmaster.Resulting behavior
mdbooknow writes where the deploy step already expects artifacts to exist.{ "scripts": { "mdbook": "mdbook build tutorials --dest-dir out/tutorials" } }