tiagobento opened a new issue, #3811: URL: https://github.com/apache/incubator-kie-tools/issues/3811
Merge queues are something that's been in the industry for a while, but mostly for huge teams and very complex git systems. Some companies even have their own forks of git, and depend on proprietary or closed-source 3rd party solutions to provide some services for them. Shopify, for example, has implemented their own "Merge queues" a while ago. See: - https://www.youtube.com/watch?v=04TTRJArpVw; and - https://shopify.engineering/successfully-merging-work-1000-developers This is coming to the general public now, with GitHub Merge Queues [1]. The main problem it solves is semantic conflicts and stale PR builds. Since `kie-tools` is a monorepo, and we currently have a growing community with reasonable-sized teams contributing to it, I see us gaining a huge benefit with Merge Queues. Semantic conflicts are often hard to solve, and most of the time, hard to identify. When they happen, all PR merges must be halted until it's solved, which generates some stress and potentially delays to the development cycle. [1] https://github.blog/changelog/2023-02-08-pull-request-merge-queue-public-beta/ -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
