@iivvaall ,
I change the .github/workflows/runner.yaml in the PR and action is not triggered
From which branch the PR is merging? And into which branch the PR is merging?
In which branch did you change the " .github/workflows/runner.yaml" file?
According to the configurations of the triggers in your workflow, the workflow can be triggered in the following situations:
1) Directly push commits to the master branch, and at least one modified file in the commits can match the patterns (’ runner/**’ or ’ .github/workflows/runner.yaml’) of the paths filter. In this situation, the workflow YAML file must have been existing in the master branch, and the workflow is triggered by the Push event.
2) After pushing some commits in a branch (not the master branch, suppose it’s named " develop"), when creating and opening a PR to merge the commits from the develop branch into the master branch, at least one modified file in the commits can match the patterns (’ runner/**’ or ’ .github/workflows/runner.yaml’) of the paths filter. In this situation, the workflow YAML file must have been existing in the develop branch, and the workflow is triggered by the Pull Request event ( Activity type: opened ).
3) After opening the PR (the PR is " Open" status), when you push some commits to the develop branch, at least one modified file in the commits can match the patterns (’ runner/**’ or ’ .github/workflows/runner.yaml’) of the paths filter. In this situation, the workflow YAML file must be existing in the develop branch, and the workflow is triggered by the Pull Request event ( Activity type: synchronize ).
4) If you close the PR without merged (the PR is " Closed" status, not " Merged" status), then reopen this PR. In this situation, the workflow YAML file must be existing in the develop branch, and the workflow is triggered by the Pull Request event ( Activity type: reopened ).
So, please confirm whether it satisfies any of the above situations, when you change the " .github/workflows/runner.yaml" file.
In addition, if you run a workflow to modify and push files with using the GITHUB_TOKEN to authenticate, events triggered by the GITHUB_TOKEN will not create a new workflow run. This prevents you from accidentally creating recursive workflow runs (see here).