❗ GitHub → Taiga webhook via GitHub Actions not triggering any updates

Hi everyone!

I want to configure a GitHub webhook that triggers only for the main branch.
I’m trying to trigger a Taiga webhook from a GitHub Actions workflow whenever I push to the main branch — but although Taiga returns 204 No Content, nothing actually happens inside the Taiga project (no new post).

(I’m on the web version of Taiga)

Here is my workflow:

name: Notify Taiga on main push

on:
  push:
    branches: ["main"]

permissions:
  contents: read

jobs:
  notify:
    runs-on: ubuntu-latest

    steps:
      - name: Copy GitHub event payload
        run: cp "$GITHUB_EVENT_PATH" payload.json

      - name: Compute SHA1 signature
        id: sig
        env:
          TAIGA_WEBHOOK_SECRET: ${{ secrets.TAIGA_WEBHOOK_SECRET }}
        run: |
          SIG=$(python3 -c "import hmac, hashlib, os; secret=os.environ['TAIGA_WEBHOOK_SECRET'].encode(); data=open('payload.json','rb').read(); print(hmac.new(secret,data,hashlib.sha1).hexdigest())")
          echo "Computed signature: $SIG"
          echo "signature=sha1=$SIG" >> $GITHUB_OUTPUT

      - name: Send payload to Taiga
        env:
          TAIGA_WEBHOOK_URL: ${{ secrets.TAIGA_WEBHOOK_URL }}
          SIGNATURE: ${{ steps.sig.outputs.signature }}
        run: |
          echo "Sending with signature: $SIGNATURE"
          curl -v "$TAIGA_WEBHOOK_URL" \
            -H "Content-Type: application/json" \
            -H "X-Hub-Signature: $SIGNATURE" \
            --data-binary @"payload.json"

:yellow_circle: Question:
Has anyone successfully triggered Taiga’s github-hook endpoint from GitHub Actions?
Does Taiga require a specific subset of GitHub events or headers?
Is the 204 response normal even when the event is ignored?

Any hints or examples would be super helpful :folded_hands: