entrypoint.sh assumes "on: push" about sonarqube-action HOT 3 CLOSED

Thank you for raising a issue to us so promptly. Please make sure you have given us as much context as possible.

We will try and get back to you as soon as possible.

from sonarqube-action.

No, you are responding wrongly. When someone opens PR, the workflow will perform two actions: with push & PR. Once the first action is executed, we no longer need to run the options afterwards, which will overwrite the analysis on SonarQube itself - so the timeline order doesn't match. Therefore you can also select trigger on on-push or on-pull_request.

from sonarqube-action.

My point is, that I would like to use the action with a workflow that does not trigger on push, therefore the push event from the PR is ignored and the IF condition stops the trigger from the second event. My workflow looks like this:

name: sonarqube

on: [workflow_dispatch, pull_request]

jobs:
  sonarQubeTrigger:
    name: SonarQube Trigger
    runs-on: ubuntu-latest
    steps:
    - uses: actions/checkout@master
    - name: SonarQube Scan
      uses: kitabisa/sonarqube-action@master
      with:
        projectKey: MyProjectKey
        host: ${{ secrets.SONARQUBE_HOST }}
        login: ${{ secrets.SONARQUBE_TOKEN }}
      env:
        GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}

There is no analysis on SonarQube triggered from the PR. Only via the workflow_dispatch can I trigger it, in this workflow.

from sonarqube-action.