On Push Tags '*' Triggered in one repository, not in another one

I created an action like this:

name: Build Release

    - '*'


    runs-on: ubuntu-latest
    - name: Set env
      shell: bash
      run: echo "RELEASE_VERSION=${GITHUB_REF#refs/*/}" >> $GITHUB_ENV
    - name: Checkout repository
      uses: actions/checkout@v2
    - name: Create dist folder
      shell: bash
      run: |
        mkdir dist
    - name: Set version
      shell: bash
      run: |
        echo "VERSION_STRING = '${{ env.RELEASE_VERSION }}'" > addon/version.py
    - name: Zip
      shell: bash
      run: |
        cd addon
        zip -r ../dist/${{ env.RELEASE_VERSION }}.zip .
        cd ..
    - name: Upload artifacts
      uses: ncipollo/release-action@v1
        artifacts: "dist/*"
        allowUpdates: true
        token: ${{ secrets.GITHUB_TOKEN }}

On the main repo where I want to deploy the action, it is not triggered at all when pushing a new tag.
I pushed the exact files of that repo to another, new repo and there it triggers just fine when a new tag is pushed.

The only difference between those two repositories is that the one where it doesn’t work has a longer git history and more collaborators added (could that causes issues with secrets.GITHUB_TOKEN?).

Anybody can give me a hint what the difference between these repositories might be which causes it to break?

Are the tags of the same format? I’m wondering if in one case there might be a character that '*' doesn’t match (in particular, a slash). In that case you’ll need to use '**'. See also the filter pattern cheat sheet.

I used the same tag to test in both repos: 1.0.0-alpha.1

Seems like that should be caught by '*'?

Yes, that should work, so I guess it’s a less-obvious reason. :sweat_smile:

Can you share links to the repositories and workflows so people here can take a look?