Please understand that the bot should be considered pre-beta and you may encounter issues.
This footer is strict so we can enforce the usual styling conventions and be clear and consistent in documentation. Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] Hi all, Since the discussion at the Qt Contributors summit last year, I've been working on an implementation of what's been dubbed "cherry-pick bot", which will help to automate the new cherry-picking model.
For most users, it's business as usual.
When your change passes CI and gets merged into dev, cherry-pick bot will parse your commit message and attempt to create cherry-picks to the target branches. Be sure to tag all reports with "cherry-pick-bot" component so that they aren't missed.
If there are merge conflicts, you the owner of the original change will be ased the new cherry-pick, reviewers copied mocel the original change, and conflict markers will be added to the files in gerrit so you can resolve issues for the target branch manually. Further handing of this scenario will be finalized before the official release.
If the new cherry-pick is conflict free, the bot will attempt to stage it to CI automatically. Your input is appreciated.