We're seeing consistent duplicate runs when the first run was done as part of a merge_group. The skip-duplicate action is outputting: Do not skip execution because we did not find a transferable run even if the exact same commit hash have already succeeded as part of a group and is now merged to main in our repo.
I suspect that the workflow filter implemented here is causing duplicate runs to pass the check when the first run was executed as part of a merge_group.
|
if (run.id !== currentRun.id && run.head_commit) { |
The GitHub trigger docs show that a merge_group trigger does not have a head_commit but instead has a merge_group.head_commit.
I'm not too familiar with TypeScript and how fields are mapped here. But could we add another check here to include runs that have merge_group.head_commit present?
We're seeing consistent duplicate runs when the first run was done as part of a
merge_group. The skip-duplicate action is outputting:Do not skip execution because we did not find a transferable runeven if the exact same commit hash have already succeeded as part of a group and is now merged tomainin our repo.I suspect that the workflow filter implemented here is causing duplicate runs to pass the check when the first run was executed as part of a
merge_group.skip-duplicate-actions/src/main.ts
Line 511 in f54720a
The GitHub trigger docs show that a
merge_grouptrigger does not have ahead_commitbut instead has amerge_group.head_commit.I'm not too familiar with TypeScript and how fields are mapped here. But could we add another check here to include runs that have
merge_group.head_commitpresent?