that it looks like
>> >>>> issue_comment is mutually exclusive with the other events. For example,
>> >>>> given the following flow
>> >>>>
>> >>>> name: Java Tests
>> >>>> on:
>> >>>>
'examples/kotlin/**', 'release/**', 'buildSrc/**']
> >>>> issue_comment:
> >>>> types: [created]
> >>>>
> >>>> jobs:
> >>>> pr_commented:
> >>>> # This job
t comments
>>>> name: PR comment
>>>> if: ${{ github.event.issue.pull_request }}
>>>> runs-on: ubuntu-latest
>>>> steps:
>>>>- run: |
>>>> echo A comment on PR $NUMBER
>>>
- run: |
>>> echo A comment on PR $NUMBER
>>> env:
>>>NUMBER: ${{ github.event.issue.number }}
>>>
>>> issue_commented:
>>> # This job only runs for issue comments
>>> name: Issue comment
&g
ssue.number }}
>>
>> issue_commented:
>> # This job only runs for issue comments
>> name: Issue comment
>> if: ${{ !github.event.issue.pull_request }}
>> runs-on: ubuntu-latest
>> steps:
>> - run: |
>>
> the flow will get kicked off but upon validating the if conditional,
> neither job will run since the github.event.issue.pull_request parameter is
> not present.
>
> Another caveat is that we'd have to populate with an if statement every
> job we wanted to execute by way
NUMBER: ${{ github.event.issue.number }}
the flow will get kicked off but upon validating the if conditional,
neither job will run since the github.event.issue.pull_request parameter is
not present.
Another caveat is that we'd have to populate with an if statement every job
we wanted
