The problem I have is that when a merge commit contains [ci skip] then the merge commit is not built as is expected, but instead the previous commit is built which is unexpected. When [ci-skip] is used, I assume no travis build is triggered at all. You can see this better with an image here: [Ima…

We’ve pushed the fix. [image] [skip ci] command is respected under all circumstances - Travis CI changelog We fixed a bug where we build an incorrect commit when multiple commits are pushed at once but the last commit...

[ci skip] in merge commit builds previous commit

Travis CI Discussions & Feedback

BanzaiMan January 13, 2020, 2:32pm 14

We’ve pushed the fix.

1 Like

Topic		Replies	Views
[skip travis] ignored Travis CI Discussions & Feedback	5	734	November 29, 2019
Github PR blocked due to [skip CI] message Travis CI Discussions & Feedback github-integration , travis-build , bug	1	600	July 9, 2020
Build delays when merging Pull requests Travis CI Discussions & Feedback	2	49	August 28, 2024
Travis skip fails Enterprise commit-message	10	5811	July 16, 2019
Travis CI Not Triggering Build After Push – Need Help! Early Releases	1	1506	October 28, 2023

[ci skip] in merge commit builds previous commit

Related topics