From ea9a6faf86e346859c4ba4278662ec35cbc32d26 Mon Sep 17 00:00:00 2001 From: Tom French <15848336+TomAFrench@users.noreply.github.com> Date: Wed, 27 Mar 2024 23:05:57 +0000 Subject: [PATCH] chore: pass release PR number to sticky comment action (#4665) # Description ## Problem\* Resolves ## Summary\* See comment ## Additional Context ## Documentation\* Check one: - [x] No documentation needed. - [ ] Documentation included in this PR. - [ ] **[For Experimental Features]** Documentation to be submitted in a separate PR. # PR Checklist\* - [x] I have tested the changes locally. - [ ] I have formatted the changes with [Prettier](https://prettier.io/) and/or `cargo fmt` on default settings. --- .github/workflows/release.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/.github/workflows/release.yml b/.github/workflows/release.yml index 8ab5c182ef2..badcd3af2dd 100644 --- a/.github/workflows/release.yml +++ b/.github/workflows/release.yml @@ -116,6 +116,7 @@ jobs: if: ${{ always() }} needs: + - release-please - update-acvm-workspace-package-versions - update-docs @@ -127,6 +128,8 @@ jobs: - name: Add warning to sticky comment uses: marocchino/sticky-pull-request-comment@v2 with: + # We need to specify the PR on which to make the comment as workflow is triggered by push. + number: ${{ fromJSON(needs.release-please.outputs.release-pr).number }} # delete the comment in case failures have been fixed delete: ${{ !env.FAIL }} message: "The release workflow has not completed successfully. Releasing now will result in a broken release"