<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=utf-8" />
</head>
<body dir="auto">
<div>+1<br /><br />-<br />abstractj<br /></div>
<div><br />
On Jul 16, 2013, 6:26 PM, Douglas Campos wrote:
<br /><br /></div>
<blockquote type="cite">
<div>
On Tue, Jul 16, 2013 at 03:09:55PM -0500, Kris Borchers wrote:<br /><blockquote type="cite">I would like to propose we only run Travis on changes to master (push,<br />PR, etc). The problem I am having is pushing broken code to branches<br />for review, testing, etc. is causing Travis to mark the repo as broken<br />in the status image which is not true. Anyone have any other thoughts<br />on this or feel that Travis breaking on branches is at all useful?<br /></blockquote>+1<br /><br />I tend to lazily push branches while I'm fixing stuff (and waiting for<br />travis feedback), but I'm fine with travis only running on the branch<br />when I actually open the PR.<br /><br />-- <br />qmx<br />_______________________________________________<br />aerogear-dev mailing list<br />aerogear-dev@lists.jboss.org<br />https://lists.jboss.org/mailman/listinfo/aerogear-dev<br />
</div>
</blockquote>
</body>
</html>