Hi, Currently there's also the "Require branches to be up to date before merging" option activated.
I think this option is quite painful because it requires travis to rerun all the time which takes a lot of time, introduces many merge commits and at the same time adds very little protection (I'm not aware of a single pull request where it would have been useful. Ever.). Any objections to disabling this option? Matthias On 2/23/19 2:24 AM, Nyall Dawson wrote: > Hi all, > > Just a heads up: now that 3.4 is officially the LTR, I've enabled > github branch protection on the branch. This means all commits to the > branch must now: > 1. Go through a PR > 2. Pass all Travis tests > 3. Be approved by at least 1 other core committer > > (same rules as were in place for 2.18) > > Nyall > _______________________________________________ > QGIS-Developer mailing list > [email protected] > List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer > Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer > _______________________________________________ QGIS-Developer mailing list [email protected] List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
