Cherry picking an MR causes two build pipelines to be created

Steps to Reproduce

1. Cherry-pick a merged MR to an existing branch (target-branch) (auto-creating the MR or not does not affect this issue)

What is Expected

1. A new branch is created from the target-branch.
2. The merge commit is cherry-picked onto the new branch .
3. A build pipeline is started on the new branch.

What actually happens

1. A new branch is created from the target-branch.
2. A build pipeline is started on the new branch. (This is the incorrect step)
3. The merge commit is cherry-picked onto the new branch .
4. A build pipeline is started on the new branch.

Why this is a bug

When using git branches from the command line, I do push the new branch before making any changes to it. The bug effectively causes twice the number of resources to be consumed, which can be especially apparent if a CI pipeline causes a lot of resources to be consumed (time, storage, bandwidth, etc) or only run CI job can execute at one time (i.e. contention of resources).