Bugfix/563 fix merge gate

[ArBridgeman]

closes #563

Checklist

Note: If any of the items in the checklist are not relevant to your PR, just check the box.

For any Pull Request

Is the following correct:

• the title of the Pull Request?
• the title of the corresponding issue?
• there are no other open Pull Requests for the same update/change?
• that the issue which this Pull Request fixes ("Fixes...") is mentioned?

When Changes Were Made

Did you:

• update the changelog?
• update the cookiecutter-template?
• update the implementation?
• check coverage and add tests: unit tests and, if relevant, integration tests?
• update the User Guide & other documentation?
• resolve any failing CI criteria (incl. Sonar quality gate)?

When Preparing a Release

Have you:

• thought about version number (major, minor, patch)?
• checked Exasol packages for updates and resolved open vulnerabilities, if easily possible?

[tomuben]

Hm, does this really work. Because in happy day scenario, no step would be executed at all....

[tkilias]

That was what we did in ai-lab, the difference is the if: ${{ !cancelled() }} and the two paths for failure and else

  gate-2:
    if: ${{ !cancelled() }}
    name: Gate 2 - Allow Merge
    runs-on: ubuntu-24.04
    needs: [ run-unit-tests, run-integration-tests, run-stable-notebook-tests, run-stable-gpu-notebook-tests ]
    steps:
      - name: Branch Protection - failure if any ancestor failed
        if: ${{ contains(needs.*.result, 'failure') }}
        run: |
          echo '${{ toJSON(needs) }}'
          exit 1
      - name: Branch Protection
        run: true

[ArBridgeman]

Ah, thanks. Yeah, I wasn't sure from what was written what was critical or not.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud