ci: setup action for cherrypick

[zirain]

1. setup action for cherrypick by using https://github.com/carloscastrojumo/github-cherry-pick-action
2. see demo from [release/v0.4] updat title&body zirain/test-action#9
3. this action should be updated per release
4. will cerate cherrypick/release-v0.4 later

NOTE: label(e.g. cherrypick/release-v0.4) should be added before merging PR.

cc @AliceProxy @arkodg @Xunzhuo

BTW, need enable following options:

[codecov]

Codecov Report

Merging #1312 (5808298) into main (2bf9607) will increase coverage by 0.04%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main    #1312      +/-   ##
==========================================
+ Coverage   61.79%   61.83%   +0.04%     
==========================================
  Files          76       76              
  Lines       10718    10718              
==========================================
+ Hits         6623     6628       +5     
+ Misses       3648     3645       -3     
+ Partials      447      445       -2     

see 2 files with indirect coverage changes

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

[Xunzhuo]

It can only work for one release version? Like if we update this with v0.4.0, we can only cherry-pick commits to v0.4.0, but if I want to cherry-pick commits to v0.3.0, v0.2.0 ... It can not work, right?

[zirain]

It can only work for one release version? Like if we update this with v0.4.0, we can only cherry-pick commits to v0.4.0, but if I want to cherry-pick commits to v0.3.0, v0.2.0 ... It can not work, right?

Actually, I think we can make it more generic.

For now, RM (release manager) is different for each release.
Send a PR to copy these parts when RM is confirmed.
When a release is EOL, just remove those lines.

[arkodg]

this approach sgtm, another one im seeing is https://github.com/sqren/backport/tree/main

[zirain]

this approach sgtm, another one im seeing is https://github.com/sqren/backport/tree/main

it looks like a CLI, not a Github action?

[arkodg]

this approach sgtm, another one im seeing is https://github.com/sqren/backport/tree/main

it looks like a CLI, not a Github action?

yeah its a CLI + GH action https://github.com/sqren/backport-github-action

[zirain]

@arkodg so you think https://github.com/sqren/backport-github-action is better?
if so will you send a PR for that, I will close this.

[arkodg]

LGTM thanks, good to add some guidance in release steps as a follow up to this PR

[zirain]

@AliceProxy you're RM of v0.4, can you take a look at this?

[Xunzhuo]

It can only work for one release version? Like if we update this with v0.4.0, we can only cherry-pick commits to v0.4.0, but if I want to cherry-pick commits to v0.3.0, v0.2.0 ... It can not work, right?

Actually, I think we can make it more generic.

For now, RM (release manager) is different for each release. Send a PR to copy these parts when RM is confirmed. When a release is EOL, just remove those lines.

Can we document these points in release proccess ?

[zirain]

@Xunzhuo done

[Xunzhuo]

I think we need an approval from @AliceProxy

[AliceProxy]

Sorry, I was occupied with Kubecon pretty much all last week and I didn't notice this today before I released v0.4.0. In general though I'm a +1 for this system for future releases.

[zirain]

@AliceProxy can you give a approval to get this PR in?