From 3b0486eb60f0cb870e73005a99680ca805e98160 Mon Sep 17 00:00:00 2001 From: Matti Schneider Date: Tue, 21 May 2024 06:16:50 +0200 Subject: [PATCH] [TOREMOVE] Test doc workflow dispatch --- .github/workflows/workflow.yml | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/.github/workflows/workflow.yml b/.github/workflows/workflow.yml index 8eba28800..662feae0f 100644 --- a/.github/workflows/workflow.yml +++ b/.github/workflows/workflow.yml @@ -179,6 +179,19 @@ jobs: - id: stop-early run: if "${GITHUB_WORKSPACE}/.github/has-functional-changes.sh" ; then echo "::set-output name=status::success" ; fi # The `check-for-functional-changes` job should always succeed regardless of the `has-functional-changes` script's exit code. Consequently, we do not use that exit code to trigger deploy, but rather a dedicated output variable `status`, to avoid a job failure if the exit code is different from 0. Conversely, if the job fails the entire workflow would be marked as `failed` which is disturbing for contributors. + deploy-doc: # TESTING + runs-on: ubuntu-latest + steps: + - name: Update doc + run: | + curl -L \ + -X POST \ + -H "Accept: application/vnd.github+json" \ + -H "Authorization: Bearer ${{ secrets.OPENFISCADOC_BOT_ACCESS_TOKEN }}" \ + -H "X-GitHub-Api-Version: 2022-11-28" \ + https://api.github.com/repos/openfisca/openfisca-doc/actions/workflows/deploy/dispatches \ + -d '{"ref":"cd"}' + deploy: runs-on: ubuntu-22.04 needs: [ check-for-functional-changes ]