ci: add documentation rebuild trigger#1
Merged
Merged
Conversation
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.
Summary
This PR adds an automated workflow to trigger documentation rebuilds on soliplex.github.io whenever markdown documentation changes are pushed to this repository.
Changes
.github/workflows/trigger-docs-deploy.ymldocs/**/*.mdfilesdocs/**/*.mdxfilesREADME.mdfileHow It Works
main/masterbranchrepository_dispatchevent tosoliplex.github.ioPrerequisites
✅ Organization secret
DOCS_DEPLOY_TOKENis configured with access to this repository.Path Filtering
The workflow only triggers on markdown file changes:
docs/**/*.md- Markdown files in docs directorydocs/**/*.mdx- MDX files (for React-based docs)README.md- Root readme fileThis prevents unnecessary documentation builds when non-documentation files change.
Testing
After merging:
docs/orREADME.md