From 2cf9f4c5ac2ced6a698166f4a30456e3eede4071 Mon Sep 17 00:00:00 2001 From: Myron Marston Date: Mon, 24 Feb 2025 16:45:06 -0800 Subject: [PATCH] Allow `Update Gem Version Artifacts` workflow to trigger CI build. Both #225 and #226 received updated commits from the `Update Gem Version Artifacts` workflow, but the CI build did not run in either case. This should fix it so that it runs. --- .github/workflows/ci.yaml | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/.github/workflows/ci.yaml b/.github/workflows/ci.yaml index c4930eae..04c7aefe 100644 --- a/.github/workflows/ci.yaml +++ b/.github/workflows/ci.yaml @@ -7,6 +7,16 @@ on: branches: - main pull_request: + # To avoid infinite workflow loops, a PR update triggered by one workflow will not + # automatically run other workflows. + # + # The `Update Gem Version Artifacts` workflow pushes new commits to dependabot PRs, + # and we need to run the CI build on those commits so we can judge whether or not it + # is safe to merge. To enable that, we have to opt-in to having this CI workflow run + # when `Update Gem Version Artifacts` completes. + workflow_run: + workflows: ["Update Gem Version Artifacts"] + types: [completed] env: # It's recommended to run ElasticGraph with this option to get better performance. We want to run