Skip to content

ci: add documentation rebuild trigger#1

Merged
bd-mkt merged 1 commit into
mainfrom
docs/add-rebuild-trigger
Jan 9, 2026
Merged

ci: add documentation rebuild trigger#1
bd-mkt merged 1 commit into
mainfrom
docs/add-rebuild-trigger

Conversation

@bd-mkt

@bd-mkt bd-mkt commented Jan 9, 2026

Copy link
Copy Markdown
Contributor

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

  • Adds .github/workflows/trigger-docs-deploy.yml
  • Triggers on changes to:
    • docs/**/*.md files
    • docs/**/*.mdx files
    • README.md file
    • The workflow file itself

How It Works

  1. When markdown documentation changes are pushed to main/master branch
  2. This workflow sends a repository_dispatch event to soliplex.github.io
  3. The main documentation site rebuilds automatically with the latest changes
  4. Updated documentation is deployed to https://soliplex.github.io/

Prerequisites

✅ Organization secret DOCS_DEPLOY_TOKEN is configured with access to this repository.

Path Filtering

The workflow only triggers on markdown file changes:

  • docs/**/*.md - Markdown files in docs directory
  • docs/**/*.mdx - MDX files (for React-based docs)
  • README.md - Root readme file
  • ❌ Code files, images, configs, etc. will NOT trigger

This prevents unnecessary documentation builds when non-documentation files change.

Testing

After merging:

  1. Make a change to any markdown file in docs/ or README.md
  2. Push to main branch
  3. Check soliplex.github.io Actions to see the documentation rebuild
  4. Verify the changes appear on the live site within 2-3 minutes

@bd-mkt bd-mkt merged commit 0256f89 into main Jan 9, 2026
7 of 8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant