I agree it’s not ideal, but it is a common convention.

As an alternative that doesn’t clutter history, GitLab supports ignoring via the “ci.skip” git push option:

git push --push-option=ci.skip

I’m not sure what the Mercurial equivalent would be.

https://git-scm.com/docs/git-push#Documentation/git-push.txt---push-optionltoptiongt

https://docs.gitlab.com/ee/ci/yaml/#skipping-jobs

> On Nov 6, 2019, at 3:04 AM, Malcolm Matalka <malcolm.matalka@acsl.se> wrote:
> 

Several build services parse commit messages containing "[skip ci]" as a way to not start a build after push. Is there any interest in having this added to scm.sr.ht?

If so, would submit.py be the place to add it?

https://git.sr.ht/~sircmpwn/scm.sr.ht/tree/master/scmsrht/submit.py

Thanks,
Jason