From 3a6119a29096957532f0c69f6450279971d49608 Mon Sep 17 00:00:00 2001 From: Florent Poinsard Date: Mon, 26 Sep 2022 08:46:17 +0200 Subject: [PATCH] Addition of a comment in the upgrade vitess deps workflow Signed-off-by: Florent Poinsard --- .github/workflows/upgrade-vitess-dependency.yaml | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/.github/workflows/upgrade-vitess-dependency.yaml b/.github/workflows/upgrade-vitess-dependency.yaml index 0243d601..5fd7c9dc 100644 --- a/.github/workflows/upgrade-vitess-dependency.yaml +++ b/.github/workflows/upgrade-vitess-dependency.yaml @@ -1,3 +1,9 @@ +# This workflow creates a Pull Request that upgrades the Vitess Dependency of the vitess-operator. +# Because of the issue documented in https://github.com/peter-evans/create-pull-request/issues/48, +# a workflow cannot trigger the execution of other workflows when it creates a PR. +# The workaround we use to trigger the workflows on the new PR is to manually close and reopen the PR. +# https://github.com/peter-evans/create-pull-request/blob/main/docs/concepts-guidelines.md#workarounds-to-trigger-further-workflow-runs + name: upgrade-vitess-dependency on: