How to Skip a GitLab CI Pipeline with a Commit Message

GitLab skips creating a pipeline when the commit message contains a skip token or you pass the ci.skip push option.

Put [skip ci] (or [ci skip]) in the commit message, or pass -o ci.skip on git push. Both prevent the pipeline from being created for that push.

Commit-message and push-option skip

Either the message token or the push option stops the pipeline from being created.

# Commit message token
git commit -m "chore: bump version [skip ci]"

# Or skip via push option without touching the message
git push -o ci.skip

Gotchas

• Skip tokens are case-insensitive ([skip ci], [ci skip]) and must appear in the commit message of the pushed commit.
• Skipping prevents the pipeline from being created - there is no pipeline to show a status, which can block MRs that require a passing pipeline.
• ci.skip only affects that push; scheduled and API-triggered pipelines ignore commit-message skip tokens.

Related guides