Anyone know how to make Travis to be smarter about building branches that are PRed against the same repo? Currently it builds everything twice, once for the branch push, and once for the PR update. Such a waste :(

@dshafik But it makes sense. One Build to see whether the current branch builds OK and one build to see whether the merged branch will still be OK. Both can be broken independently from one another. You could argue that building the current branch is obsolete after creating a PR but as that's the only one you can change to get a green build it makes sense IMO.

Sign in to participate in the conversation
Mastodon for Tech Folks

This Mastodon instance is for people interested in technology. Discussions aren't limited to technology, because tech folks shouldn't be limited to technology either! We adhere to an adapted version of the TootCat Code of Conduct and have documented a list of blocked instances. Ash is the admin and is supported by Fuzzface, Brian!, and Daniel Glus as moderators. Hosting costs are largely covered by our generous supporters on Patreon – thanks for all the help!