Hi Yong, Awesome~ I just can't wait to try it. Best Regards, Jennifer
On Wed, Oct 28, 2020 at 7:37 PM Enrico Olivelli <eolive...@gmail.com> wrote: > In BookKeeper project we have a script that does the merge to the target > branch, handles cherry picks and also updates GitHub milestones and labels > > it should work well on Pulsar Repository as well > > https://github.com/apache/bookkeeper/blob/master/dev/bk-merge-pr3.py > > Enrico > > Il giorno mer 28 ott 2020 alle ore 11:55 Yuva raj <uvar...@gmail.com> ha > scritto: > > > This is awesome! > > > > On Wed, 28 Oct 2020 at 16:22, Yong Zhang <zhangyong1025...@gmail.com> > > wrote: > > > > > Hi developers, > > > I want to introduce a command for cherry-picking PRs automatically. > > > > > > When we releasing a minor version of Pulsar, we need to cherry-pick the > > bug > > > fix PRs > > > into the release branch. Cherry-pick a lot of PRs will take a long > time > > > and sometimes there has > > > some conflict need to resolve. > > > > > > I want to introduce a cherry-pick command which is similar to the rerun > > > test command to make the > > > cherry-pick process automatically. Ideally, after merging a PR, just > need > > > to comment `/pulsarbot > > > cherry-pick this pr into branch-2.6`, then it will open a new PR to > merge > > > into the `branch-2.6`. > > > > > > Open a new PR to do this will make that change also run the CI test in > > the > > > release branch > > > to ensure the branch can build successfully. And because the merged PR > > will > > > cherry-pick into > > > the release branch as soon as possible, we won't need to do the > > cherry-pick > > > when we release a > > > new minor version. That will reduce a lot of work for the committers. > > > > > > If you have any suggestions please let me know. > > > > > > Thanks, > > > Yong > > > > > > > > > -- > > *Thanks* > > > > *Yuvaraj L* > > >
