Post

Is *anyone* using "Require branches to be up to date before merging" ? Always saw this setting as pretty harmful (N people update their branch in the hope to merge, only one can, all others wasted their CI time; rinse and repeat).

0 reposts0 likes

We turned it off. It was annoying any not valuable enough. Running some of ci just before deploy is enough to be safe and main is very rarely red.

Oh my... I probably turned that toggle on 8 years ago without fully grasping the impact and spend the last 5 years frustrated thinking forgeting we even had the choice. Thanks to your post, I realised we don't have to live that way 🤣. Thank you for drawing my attention to this 🙏.

yeah, it's an unusable feature when you have a slightly long CI time (3-5 min) and many PRs being merged at the same time - we had it on for a while and we quickly shut it down, super annoying

I don't understand why GH doesn't provide "max age" / "max depth" / "checkpoint commit" mechanisms to make this more acceptable to high-velocity repositories.