Hello, Christopher Baines <m...@cbaines.net> writes:
> It isn't obvious to me what the best approach is though, maybe ordering > branches to be merged could be handled through Pull Requests, or maybe > we could put in place a generated branch system, where the changes in > Pull Requests can be grouped together through a Milestone and ordered > via the Pull Request Dependencies, which I think could have some key > advantages. A comprehensive plan for the minimal viable approach is > needed though. A pull request is a branch, so I’d be inclined to do away with the “Request for merging” mechanism; a pull request *is* a request for merging. :-) Now, pull requests that trigger lots of rebuilds shouldn’t be built right away. Instead, we probably need a mechanism where any PR with more than N rebuilds does not get built unless some human being explicitly allows it. WDYT? Ludo’.
