[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Master is broken

Hi folks,

The master branch has been broken for a couple of days already. But that
hasn't stopped the project from merging pull requests. As time passes by,
it gets hard to identify what change caused the breakage. And of course,
fixing it might cause conflicts with the changes introduced by the merged

It seems to me that there should be some sort of process or guidelines in
place to avoid this sort of situations. "Don't merge if master is red"
seems like a reasonable option.

If this guideline sounds obvious enough that it shouldn't be spelled out in
the commiters' documentation, then that's fine, but it hasn't been followed


Gerardo Curiel //

( ! ) Warning: include(msgfooter.php): failed to open stream: No such file or directory in /var/www/git/apache-airflow-development/msg03632.html on line 88
Call Stack
10.0006362984{main}( ).../msg03632.html:0

( ! ) Warning: include(): Failed opening 'msgfooter.php' for inclusion (include_path='.:/var/www/git') in /var/www/git/apache-airflow-development/msg03632.html on line 88
Call Stack
10.0006362984{main}( ).../msg03632.html:0