Merge Queue 101 // Predictive Testing // How does a Merge Queue work? // trunk.io/merge
The core concept of any merge queue is predictive testing. The idea here is to test your pull request against the head of your protected branch main and all the pull requests ahead of your own in the queue.
How does a merge queue work?
Instead of merging your pull requests directly through GitHub/GitLab, engineers submit their pull requests to a merge queues service. A pull request can be submitted to the queue before passing CI or code review is complete. Once the pre-requisites for the queue have been met - the pull request will formally enter the queue.
A merge queue will test your pull request against the changes ahead of it in the queue so that the changes are tested against the predicted view of the branch, assuming everything ahead of it merges successfully. This process is called predictive testing and is illustrated in the video below.
When all the required tests are passing, the merge queue with merge the pull request into the protected branch automatically.
If your pull request fails testing - it will either be retested or removed from the queue for further inspection by the author.
Learn more about merge queues here:
https://docs.trunk.io/merge
Смотрите видео Merge Queue 101 // Predictive Testing // How does a Merge Queue work? // trunk.io/merge онлайн без регистрации, длительностью часов минут секунд в хорошем качестве. Это видео добавил пользователь Trunk 20 Май 2024, не забудьте поделиться им ссылкой с друзьями и знакомыми, на нашем сайте его посмотрели 76 раз и оно понравилось людям.