{"action":"opened","issue":{"url":"https://api.github.com/repos/travis-ci/travis-ci/issues/6669","repository_url":"https://api.github.com/repos/travis-ci/travis-ci","labels_url":"https://api.github.com/repos/travis-ci/travis-ci/issues/6669/labels{/name}","comments_url":"https://api.github.com/repos/travis-ci/travis-ci/issues/6669/comments","events_url":"https://api.github.com/repos/travis-ci/travis-ci/issues/6669/events","html_url":"https://github.com/travis-ci/travis-ci/issues/6669","id":180745132,"number":6669,"title":"BUG: `[ci skip]` ignored in PR merge","user":{"login":"jakirkham","id":3019665,"avatar_url":"https://avatars.githubusercontent.com/u/3019665?v=3","gravatar_id":"","url":"https://api.github.com/users/jakirkham","html_url":"https://github.com/jakirkham","followers_url":"https://api.github.com/users/jakirkham/followers","following_url":"https://api.github.com/users/jakirkham/following{/other_user}","gists_url":"https://api.github.com/users/jakirkham/gists{/gist_id}","starred_url":"https://api.github.com/users/jakirkham/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jakirkham/subscriptions","organizations_url":"https://api.github.com/users/jakirkham/orgs","repos_url":"https://api.github.com/users/jakirkham/repos","events_url":"https://api.github.com/users/jakirkham/events{/privacy}","received_events_url":"https://api.github.com/users/jakirkham/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2016-10-03T20:57:32Z","updated_at":"2016-10-03T20:57:32Z","closed_at":null,"body":"If a merged PR commit has `[ci skip]` in it's commit message, Travis CI seems to skip building that commit, but instead builds the latest commit in the PR on the base branch. This is pretty odd behavior as one would normally expect nothing to be built in this case. In fact other CIs (e.g. AppVeyor or CircleCI), do exactly that (i.e. build nothing).\r\n\r\nAs an example, consider this PR ( https://github.com/conda-forge/poliastro-feedstock/pull/2 ). It states in the PR title to `[ci skip]`. As expected, all CIs build the commits in the PR. Here's [Travis CI's build]( https://travis-ci.org/conda-forge/poliastro-feedstock/builds/164528051 ). When merging the PR, we get this merge commit ( https://github.com/conda-forge/poliastro-feedstock/commit/af5c402c262c54a27bcde0a1cec634e01ba845b7 ). It can be seen clearly that the commit message says `[ci skip]` in it. All of the CIs skip building that commit.\r\n\r\nHowever, Travis CI starts a [build]( https://travis-ci.org/conda-forge/poliastro-feedstock/builds/164566480 ) of commit ( https://github.com/conda-forge/poliastro-feedstock/commit/950d375e3da41d1b37acacc764c41954c67dc253 ), which was the last commit in the PR. If we look at the status of that [commit]( https://github.com/conda-forge/poliastro-feedstock/commits/950d375e3da41d1b37acacc764c41954c67dc253 ). We can see it has push and pr statuses from Travis CI when it should only have a pr status.\r\n\r\nIn short, it would be nice when merging a PR that has `[ci skip]` in the merge commit to have nothing build not a re-build of some previous PR commit."}}
{"actor":{"display_login":"jakirkham"}}