-
Notifications
You must be signed in to change notification settings - Fork 19
Conversation
cc: @techtonik et al. |
Ok for disabling IRC, but why don't build branches? |
Because then we end up with two Travis builds per pull request, because of the way GitHub does pull requests. If I understand it right, GitHub automatically makes a merge commit for each pull request (I presume this is how they can determine whether the branch merges cleanly or not). Since the See gratipay/gratipay.com#3187 for where we introduced this on |
I look through Travis and can't see where PR commits are built on branches. Can you show an example of these two builds? |
@techtonik Notice the two checks on #116, e.g., while there's only one check here. |
See also: travis-ci/travis-ci#3241. |
https://docs.travis-ci.com/user/pull-requests That makes it sound like if you test on all branches and you test pull requests, then you get two builds per PR (one for the branch, one for the PR merge commit) ... but if you only test the |
Now I see. |
Looks like Travis couldn't understand this request and hung. |
6fed52b
to
cf18173
Compare
Rebased. |
And merged! |
Yay! 💃 P.S. @techtonik When you rebase can you leave the commit hash of the previous head in a comment for future reference? Thanks. :-) |
But when I force push it, it is gone, no? |
@techtonik It's not listed on this PR anymore, but GitHub still keeps it around so we can browse it if we want to. |
Ok. I'll keep this in mind. |
cf. liberapay/postgres.py#57