Run VachaShah/backport@v2.2.0
with:
github_token: ***
head_template: backport/backport-<%= number %>-to-<%= base %>
body_template: Backport <%= mergeCommitSha %> from #<%= number %>.
label_pattern: ^backport (?([^ ]+))$
labels_template: []
title_template: [Backport <%= base %>] <%= title %>
Warning: Your repository allows merge commits and rebase merging.
However, Backport only supports rebased and merged pull requests with a single commit and squashed and merged pull requests.
Consider only allowing squash merging.
See https://help.github.com/en/github/administering-a-repository/about-merge-methods-on-github for more information.
Backporting 97d51f4b176745defe9f11526fff22a45faf7e5f from #653.
/usr/bin/git show -s --format='%an' 97d51f4b176745defe9f11526fff22a45faf7e5f
fatal: not a git repository (or any of the parent directories): .git
Error: Error: The process '/usr/bin/git' failed with exit code 128
Do you have any additional context?
Mostly posting this for situational awareness. I assume 2.2.0 has a bug and we should either revert to 2.1.0, or wait for 2.3.0, and in the meantime we should be alert when we merge PRs to manually backport them.
What is the bug?
After updating to
VachaShah/backport@v2.2.0
, backport workflows are failing.How can one reproduce the bug?
Merge a PR. Observe the backport workflow fail.
See: https://github.com/opensearch-project/opensearch-sdk-java/actions/workflows/backport.yml
What is the expected behavior?
Backport workflow completes.
What is your host/environment?
GitHub Actions.
Do you have any screenshots?
Do you have any additional context?
Mostly posting this for situational awareness. I assume 2.2.0 has a bug and we should either revert to 2.1.0, or wait for 2.3.0, and in the meantime we should be alert when we merge PRs to manually backport them.
CC: @VachaShah