andygrove opened a new pull request, #2177: URL: https://github.com/apache/datafusion-ballista/pull/2177
# Which issue does this PR close? <!-- No issue; small CI infrastructure fix. --> N/A # Rationale for this change The "Deploy DataFusion Ballista site" workflow (`.github/workflows/docs.yaml`) builds the docs and pushes the HTML to the `asf-site` branch that serves https://datafusion.apache.org/ballista/. It only runs `on: push` to `main` touching `docs/**`. When a push event is dropped or never fires (as happened with the benchmarking.md refresh in #2171, which merged to `main` but produced no workflow runs at all), the docs change is left unpublished and there is no way to re-trigger the deploy short of pushing another commit to `docs/`. Adding a `workflow_dispatch` trigger lets a maintainer re-run the deploy on demand from the Actions UI or `gh workflow run`, both to recover from a missed trigger and as a general safety net. # What changes are included in this PR? - Add a `workflow_dispatch:` trigger to `.github/workflows/docs.yaml`, alongside the existing `push` trigger. # Are there any user-facing changes? No. This only affects how the docs deploy workflow can be triggered. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
