[BXMSPROD-1892] Automated pr backporting reusable actions

[lampajr]

JIRA:

https://issues.redhat.com/browse/BXMSPROD-1892

referenced Pull Requests:

• [ISSUE-18] Customize cherry pick branch name carloscastrojumo/github-cherry-pick-action#26
• [BXMSPROD-1892] Automated pull request backporting workflow kiegroup/droolsjbpm-build-bootstrap#2165

Workflows PRs:

• https://github.com/kiegroup/drools/pull/4863
• https://github.com/kiegroup/kogito-runtimes/pull/2684
• https://github.com/kiegroup/kogito-examples/pull/1504
• https://github.com/kiegroup/kogito-apps/pull/1558
• https://github.com/kiegroup/optaplanner/pull/2451
• Automated pull request backporting workflow kiegroup/optaweb-employee-rostering#882
• Automated pull request backporting workflow kiegroup/optaweb-vehicle-routing#831
• https://github.com/kiegroup/optaplanner-quickstarts/pull/470
• [BXMSPROD-1892] Automated pull request backporting workflow kiegroup/optaplanner-website#560
• [BXMSPROD-1892] Automated pull request backporting workflow kiegroup/drools-website#236

Improvements:

Created two reusable actions:

• backporting: this action applies the cherry-pick and creates one or more pull requests in according to their inputs
• parse-labels: parse pull request labels extracting target branches

[lampajr]

Just for now I would replicate the same reusable actions defined in droolsjbpm-build-bootstraps [1] but as discussed here [2] we can later move them in a single place with a massive refactoring of all common actions.

[1] kiegroup/droolsjbpm-build-bootstrap#2165
[2] kiegroup/droolsjbpm-build-bootstrap#2165 (comment)

[Ginxo]

sorry guys, but, it this not the use case covered by https://github.blog/2022-02-10-using-reusable-workflows-github-actions/ ? The idea is to reuse a workflow from one centralized place, right? and not to duplicate it through all of the repositories. WDYT?

[mareknovotny]

sorry guys, but, it this not the use case covered by https://github.blog/2022-02-10-using-reusable-workflows-github-actions/ ? The idea is to reuse a workflow from one centralized place, right? and not to duplicate it through all of the repositories. WDYT?

i agree it should be in that form, but aren't there already that implemented like this? You still need to add individual yaml files for GHA registered workflows on individual repositories, right? Or am I missing something?