ci: find a way to reenable the cherry-picker process

[Manoramsharma]

What type of PR is this?

CI workflow

What this PR does / why we need it:

This PR introduces a custom GitHub Actions workflow to automate the cherry-picking of merged pull requests with a specific label into a target branch. This automation simplifies the release management process and ensures that critical changes are propagated to the necessary branches efficiently.

Which issue(s) this PR fixes:

Fixes #3946

Changes made in this PR:

• Added a new GitHub Actions workflow (cherry-picker.yml) to automate the cherry-picking process.
• The workflow is triggered when a pull request targeting the main branch is closed.
• The workflow checks if the pull request has the label cherrypick/release-v1.1 and if it was merged.
• The workflow includes steps to:
  • Checkout the repository.
  • Configure Git with the GitHub Actions bot user.
  • Cherry-pick the merge commit into the target branch release/v1.1.
  • Push the changes to the target branch.
• Ensured the workflow adheres to linting standards by removing trailing spaces and properly formatting comments.

Additional context:

This workflow helps in reducing manual effort for the release manager by automating the process of cherry-picking merged PRs with specific labels into their respective release branches.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 67.45%. Comparing base (b4b2985) to head (07acb97).
Report is 294 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #3958      +/-   ##
==========================================
+ Coverage   67.36%   67.45%   +0.09%     
==========================================
  Files         183      183              
  Lines       22443    22443              
==========================================
+ Hits        15118    15140      +22     
+ Misses       6233     6217      -16     
+ Partials     1092     1086       -6     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[zirain]

directly push to target branch is not allowed

[zirain]

can we create branch with read permission?

[Manoramsharma]

Thank you for pointing that out. I should have update the permissions in the workflow to ensure that the action can create and push branches. The permissions should be set to contents: write and pull-requests: write.

[zirain]

@Manoramsharma thanks for you work, but I think this's not a good issue for begginer(this one need a lot of collaborations with the Envoyproxy org admin).

[github-actions]

This pull request has been automatically marked as stale because it has not had activity in the last 30 days. Please feel free to give a status update now, ping for review, when it's ready. Thank you for your contributions!

[zirain]

As we discussed, we won't need this for now.
I'd like to close this first, feel free to reopen.