chore: notify docs site after benchmark data is published#804
Conversation
The previous push trigger was path-filtered on Docs/pages/**, so it never fired for benchmark data: that data is published to the 'benchmarks' branch via the GitHub API using GITHUB_TOKEN, which cannot trigger push-based workflows. Switch to a workflow_run trigger on the Build workflow completing on main (mirroring aweXpect). This notifies the site after every successful main Build, covering docs edits and benchmark updates alike, without depending on which files or branches changed.
a603476 to
41265cb
Compare
🚀 Benchmark ResultsDetails
Details
Details
Details
Details
Details
|
|
… data is published (#804) by Valentin Breuß
… data is published (#804) by Valentin Breuß



The previous push trigger was path-filtered on Docs/pages/**, so it never fired for benchmark data: that data is published to the 'benchmarks' branch via the GitHub API using GITHUB_TOKEN, which cannot trigger push-based workflows.
Switch to a workflow_run trigger on the Build workflow completing on main (mirroring aweXpect). This notifies the site after every successful main Build, covering docs edits and benchmark updates alike, without depending on which files or branches changed.