Cherrypicker not picking up release-1.14 comments

[craigbox]

Leaving a /cherrypick release-1.14 comment on istio/istio.io issues is not causing the bot to act.
Setting the cherrypick/release-1.14 label does what we want.

• Current example where commenting didn't do anything: Fix huawei Application Service Mesh link istio.io#11380
• Example of a failure where I later set the label and it worked: Wildcard egress: remove arbitrary domain section istio.io#11291
• Example of where setting only the label worked: Helm and gateway tests istio.io#11276

[GregHanson]

possibly a separate issue, but on failed cherry-picks, I have observed two attempts being made at performing the cherry-pick and therefore 2 separate issues created for each attempt.

Example:

• PR Stop previous remote cluster when updating secret istio#39367
• Issue 1: [release-1.14] Stop previous remote cluster when updating secret istio#39395
• Issue 2: [release-1.14] Stop previous remote cluster when updating secret istio#39393

Appears to have created duplicates for 1.12, 1.13 and 1.14

[craigbox]

In case it's related to release-1.14 specifically, I tried adding cherrypick/master label on a PR to that branch, and nothing happened. istio/istio.io#11395

[craigbox]

I tried both approaches in istio/istio.io#11398 and 6 hours later there's no cherrypick.

[ericvn]

I added a remark in istio/istio.io#11448 today, and the bot replied. Will be curious if the CP is created when the PR merges.

[aimuz]

istio/istio.io#12273

Setting the cherrypick/release-1.16 tag doesn't seem to work properly