[skip travis] ignored


I was pushing a few commits and included [skip travis] as part of the commit message in the HEAD commit:

1a02c00 (HEAD -> master, origin/master, origin/HEAD) Add release-drafter config\n[skip travis]
b4689a4 Enable SBT's offline mode when deploying
7fc2db9 Cache `$HOME/.coursier` directory too

Still, somehow, a build was triggered. Why?


It seems as if Travis identified the HEAD commit to be the second one instead of the top commit which is, coincidentally, the same order GitHub shows on the compare page. Is this a bug?

As you can see at https://github.com/avdv/scalals/compare/7410b1120940...1a02c00b4b7a and the build’s title, the build was triggered by the 2nd commit in the list which doesn’t have the skip note.

Yeah, I can see that. I think that’s a bug, no?!

According to https://travis-ci.com/avdv/scalals/requests , Travis received a build request from Github for the 2nd commit. That commit doesn’t have any skip notes so there was no reason for Travis not to create a build.

So if this is a bug/unexpected behavior, it’s that of Github, not Travis. Contact Github support.

We received a build request for b4689a4 ~1 hour before the build request for 8612e22, which was rejected by the command. It seems that something (it might have been you, or GutHub if you made the commit directly on GitHub.com) pushed a commit to Github.

Thanks. But, I am still wondering…

I did a git push directly onto the master branch. According to the API:

      "id": 274732221,
      "repository_id": 10903168,
      "commit_id": 272351896,
      "created_at": "2019-11-28T07:26:31Z",
      "owner_id": 923332,
      "owner_type": "User",
      "event_type": "push",
      "base_commit": null,
      "head_commit": null,
      "result": "approved",
      "message": null,
      "pull_request": false,
      "pull_request_number": null,
      "pull_request_title": null,
      "branch": "master",
      "tag": null,
      "build_id": 138526025
      "id": 272351896,
      "sha": "b4689a4e44e0df69e02497bb1b4d2748d2d6ecc0",
      "branch": "master",
      "message": "Enable SBT's offline mode when deploying",
      "committed_at": "2019-11-28T07:19:13Z",
      "author_name": "Claudio Bley",
      "author_email": "claudio.bley@gmail.com",
      "committer_name": "Claudio Bley",
      "committer_email": "claudio.bley@gmail.com",
      "compare_url": "https://github.com/avdv/scalals/compare/7410b1120940...1a02c00b4b7a",
      "pull_request_number": null

There’s no head_commit for the corresponding request. And the commit itself also has the wrong sha, but the correct compare URL (base_commit = 7410b1120940, head_commit = 1a02c00b4b7a). How come? Where does this information originate from?