Skip CI builds during git push (as opposed to commit message)
Sometimes, I will want to push code, but I know it's not ready for a CI build yet. I really don't like polluting my commit messages with "tags" like [ci skip], and it wouldn't be clear to which commit I should add this tag anyway.
It would be much better if I could somehow tell GitLab, during the git push
, to not create a build for this push event. This question on StackOverflow asks about passing arguments from git push
.
While is of course isn't directly possible, this answer sheds some light on possible ways to accomplish this. The primary way would be via the target ref. Could we possibly "alias" ciskip/ref-name
to ref-name
, with the added effect of skipping CI build creation?
This can be accomplished using git push options.
Edited by Jonathon Reinhart