I've done some more tests and the action is triggered when creating a release through the Github webpage but when creating a release through the API this event is not triggered. Feels like a bug no?
... View more
Looks like my previous comment somehow disappeared. I have the same issue where duplicate checks are generated. This becomes a big issue when using " Require status checks to pass before merging" on an action where this can happen. Let's say you have an action which is triggered by the following: on : pull_request : types : [ opened , reopened , edited , closed ] The action that is run validates the title of a Pull Request. When first opening the Pull Request the action is fired on the "opened" event and then fails that action because the title was wrong. The user now edits the Pull Request title and the action is rerun but this time with the "edited" event. This time the title was correct and the action succeeds. We now have two status checks on that Pull Request. One failed and one succeeded. Since they are not grouped together it's now impossible to merge this PR due to the "Require status checks to pass before merging" check still seeing the check that was trigged on "opened" as failed. I think that these checks should be grouped by the actual job that is selected under " Require status checks to pass before merging" and use the latest ran to set the check as successful or not.
... View more