[skip ci] still triggers workflow

I’m committing code with [skip ci] in the commit message.
On workflows that start with an approval step, these are queued as normal. If approved then the job will be skipped Your build was not run - reason code (:ci-skip).
As commits that include a commit message of [skip ci] can never be run the initial approval should never be queued & they should never show in the workflow list

Hi @timothyclarke,

Thank you for reporting this. I was able to reproduce this; the workflow does appear in the workflow list in “On Hold” status even when [skip ci] is specified in the commit message, although once approved the workflow will be in Not Run status as expected. I’ll be sharing this bug report with the team.