On Jul 16, 2013, at 11:09 PM, Kris Borchers <kris.borchers(a)gmail.com> wrote:
I would like to propose we only run Travis on changes to master
(push, PR, etc). The problem I am having is pushing broken code to branches for review,
testing, etc. is causing Travis to mark the repo as broken in the status image which is
not true. Anyone have any other thoughts on this or feel that Travis breaking on branches
is at all useful?
aerogear-dev mailing list