Repository navigation
fix(docs): validate Pages setup and isolate rerun artifacts - #28
Merged
Merged
Conversation
Contributor
Author
|
The updated workflow has passed Python CI and a manual GitHub Pages deployment on my fork. It now checks Pages configuration before building and uses a unique artifact name for each attempt to prevent conflicts on reruns. I’ve also documented the setup steps in the README. |
MUDASSIR-75
approved these changes
Oct 21, 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.
This PR improves the documentation deployment workflow by checking GitHub Pages configuration before building and preventing duplicate artifact errors when jobs are rerun.
Each deployment attempt now uses a unique artifact name, ensuring the deployment selects the correct upload. The workflow also supports manual runs, and the README explains the required Pages setup and how to run the updated workflow.
Validation completed successfully: the strict MkDocs build, Python CI, and a manual GitHub Pages deployment on the fork all passed.