c7c778f109
Code coverage and RTLMeter complete (concluding 'skipped') on branch pushes where they do no work, and each completion fires the Pages workflow_run trigger. Rebuilding and redeploying master's pages for these no-op events is wasteful. Gate the build job so a workflow_run whose upstream conclusion is 'skipped' does nothing; deploy and notify need build, so they cascade-skip. Route such no-op runs to their own throwaway concurrency group. In the shared 'pages' group they would, as the newest queued run, cancel a pending real run and then deploy nothing (concurrency keeps only the in-progress and newest pending run). Real runs keep sharing 'pages' and serialize as before. Add retry to deploy step to reduce flakyness due to the Pages back end. Fix trigger on workflow file changes. |
||
|---|---|---|
| .. | ||
| build-test.yml | ||
| contributor.yml | ||
| coverage.yml | ||
| docker.yml | ||
| format.yml | ||
| no-pulls.yml | ||
| pages.yml | ||
| reusable-build.yml | ||
| reusable-lint-py.yml | ||
| reusable-rtlmeter-run.yml | ||
| reusable-test.yml | ||
| rtlmeter.yml | ||