From 259e3fde68aa7b1df32238904b2dda544bb53e71 Mon Sep 17 00:00:00 2001 From: evazion Date: Wed, 22 Sep 2021 12:28:41 -0500 Subject: [PATCH] ci: fix issue with betabooru deploy workflow. Just trigger on pushes to the betabooru branch instead of on the Docker image being built. The workflow_run event keeps triggering on the master branch even though it's supposed to only trigger on the betabooru branch. This makes it fail because it doesn't have access to the secrets in the betabooru environment. This does mean the deploy will fail if the image hasn't been previously built by a push to master first. --- .github/workflows/deploy-betabooru.yaml | 5 +---- 1 file changed, 1 insertion(+), 4 deletions(-) diff --git a/.github/workflows/deploy-betabooru.yaml b/.github/workflows/deploy-betabooru.yaml index ed79853ac..199cf7220 100644 --- a/.github/workflows/deploy-betabooru.yaml +++ b/.github/workflows/deploy-betabooru.yaml @@ -8,14 +8,11 @@ permissions: read-all on: # https://docs.github.com/en/actions/reference/events-that-trigger-workflows#workflow_run workflow_dispatch: - workflow_run: - workflows: ["Docker Build"] - types: [completed] + push: branches: [betabooru] jobs: deploy-betabooru: - if: ${{ github.event_name == 'workflow_dispatch' || github.event.workflow_run.conclusion == 'success' }} runs-on: ubuntu-latest # https://docs.github.com/en/actions/learn-github-actions/workflow-syntax-for-github-actions#concurrency