ci: trigger Testably.Site rebuild after main build - #103
Conversation
After moving the repository to the Testably organization, documentation is centralized in Testably/Testably.Site. This workflow dispatches an `extension-documentation-updated-event` to Testably.Site whenever the Build workflow completes successfully on main, so the docs site picks up the change.
|
There was a problem hiding this comment.
Pull request overview
Adds a GitHub Actions workflow to notify the centralized documentation site repository (Testably/Testably.Site) whenever this repo’s main branch build finishes successfully, so the docs site can rebuild from the latest extension output.
Changes:
- Introduces a
workflow_run-triggered workflow that runs after theBuildworkflow completes onmain. - Dispatches an
extension-documentation-updated-eventtoTestably/Testably.Sitewith source repo and commit SHA payload. - Allows manual triggering via
workflow_dispatch(restricted tomain).
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
🚀 Benchmark ResultsDetails
|

After moving the repository to the Testably organization, documentation is centralized in Testably/Testably.Site. This workflow dispatches an
extension-documentation-updated-eventto Testably.Site whenever the Build workflow completes successfully on main, so the docs site picks up the change.