1 comment

[ 2.6 ms ] story [ 18.6 ms ] thread
This looks pretty great to me; having even a few people consistently push mostly-parallel work is a common workflow issue I see. Trunk-based development with rebase workflows arguably _needs_ a tool like this to scale contributors & velocity.

Does anyone have an understanding of how this compares to Gitlab's Merge Trains [0]? I vageuly remember trying those in a past job and thinking it wasn't as smooth as I expected, but that was several years ago.

- [0]: https://docs.gitlab.com/ee/ci/pipelines/merge_trains.html