Feature Request: A workflow should still be triggered by adding a label to a PR even if the head commit has [no ci]

[larmitage-bjss]

Select Topic Area

Product Feedback

Body

I believe this is not a bug and was intentional but I don't think it makes a lot of sense, I would not expect it to work the way it currently does.

If this is my workflow trigger:

on:
  pull_request:
    branches:
      - main
    types:
      - labeled
      - unlabeled

And I have the latest commit [no ci] made some change
And I manually add a label to the pull request

Expected behaviour

I expect the workflow to run as the latest commit on the branch is irrelevent in this scenario. The event triggering the workflow is the label being added or removed, NOT the commit being pushed.

This should also be the same on all other pull request events that aren't triggered by a commit i.e. for pull_request I think this is every type apart from synchronise

If the label was added by a workflow using the default github token, then I wouldn't expect the workflow to run

Actual behaviour

The workflow does not run until I make another (empty or otherwise) commit which does not contain [no ci] (and then add/remove the label)

An example of where this is a problem:

• I have a workflow which validates if a specific label has been added to a PR which is required to pass before merging is allowed.
• In some repos I generate documentation automatically using a workflow
• This documentation workflow either uses the default github token or a PAT (in order to update a readme in .github/workflows which cannot be done with the default token) - and so the commit message adds [no ci] to the commit message to ensure no further workflows are triggered by pushing the commit
• This means if developers forget to add the label on PR creation, the documentation workflow runs, and then there are no more changes needed to be made, the head commit has [no ci]. If the developer then adds the label, the check to ensure the PR is labeled correctly does not run and the PR cannot be merged.