FWIW, the above mentioned example fixed itself after the contributor pushed some updates to that pull request. Meaning that with the last update the Travis build status was properly communicated back.
Let’s hope that future pull-request again show the expected behavior.
@native-api - this isn’t a duplicate. There are several differences in the problem description and resolution:
First, my repository always was on travis-ci.org. The linked post explicitly just talks about travis-ci.com repositories.
Second, I didn’t see anything similar to what is described in that post and what is depicted in the screenshot.
I mean, in my repository the pull-request just looked like in a repository without any Travis-CI integration. No “some checks haven’t completed yet”, no travis-ci icon, nada.
Finally, for the pull-request (I’ve linked in my original posting) the problem fixed ‘itself’. I didn’t change any branch nor repository settings.
Also seeing this. Also not a duplicate. Branch protection settings require status checks to pass before merging using continuous-integration/travis-ci.
This is an occasional failure. Example https://github.com/gonum/gonum/pull/1290, where the push build has passed and notified, but the pr build has passed but not notified.