[aerogear-dev] Travis on branches

Kris Borchers kris.borchers at gmail.com
Tue Jul 16 16:09:55 EDT 2013


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?


More information about the aerogear-dev mailing list