@acgetchell we recently changed behavior to look for [skip ci] (and other skip strings in commit messages) only in the text before first empty line. We did that because a lot of confusion happens then people merge and squash multiple commits and single older commit prevents whole merge commit to be built. You can move [skip ci] to the first line, or make it in the second line, but without empty line before it, or you can skip commit with .md files changed as described here
Documentation is updated. Commits referenced both here and here do not not have [skip ci] in the first line of commit message. They both are after first empty line. You can open GitHub webhook content and see it yourself: part with [skip ci] will be after \n\n. Probably [skip ci] was added into description part in GitHub (or GitHub for desktop) UI, which is separated with empty line behind the scenes.
I wrote that commit message with vi and used the same format that I believe is the standard usage case:
This would be the equivalent of Commit Subject\n\nCommit Description.
The default commit message format produced by git is in that same format when doing squashes, merge commits, etc., so I don't see how the format that I'm using is wrong. It's also the "best practice" format which is recommended by most editors, and as you pointed out, the way that GitHub expects it to be.
Are you asking developers to use a different format? Like this:
If not, can you give an example of a [skip ci] commit message, which follows standard best practices, which would actually skip the CI?