Re: [emacs-w3m/emacs-w3m] Review of Travis-CI configuration is required (#11)

[Boruch Baum <notifications@xxxxxxxxxx>]

I'm not knowledgeable in travis, but I thought maybe it wasn't running because the #12 had a merge conflict, so I did an internet search based upon that premise, and confirmed that is the case:

If a pull request isn’t built or doesn’t show up in Travis CI’s user interface, that usually means that it can’t be merged. We rely on the merge commit that GitHub transparently creates between the changes in the source branch and the upstream branch the pull request is sent against.

There's more of interest on that page.

Also:

• related question on stackexchange

• conditional travis builds

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.