hmmm, I am unable to reproduce any issues with [CI SKIP] (I am using 1.0 but 0.8 has been largely frozen from changes for around 6 months). I see the following in my server logs when I include the skip directive in the commit message:
I was able to reproduce this on PRs. It looks like Drone stores the PR body message in builds.build_message, not the commit message. Sometimes on quick PRs these might be the same, but it is not always the case. This is on 1.2.3. I’ll try to work on a fix when I have some time
v.PullRequest.Body is indeed the body message of the PR. For this to work on GitHub PR commits, we’d need to pull the commits on that PR, check the latest one, and see if it has a [CI SKIP] in the message. This is a bit above my head at the moment, so I’m just leaving what I found here in case someone wants to pick it up.