Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] Backport workflow seems to have broken backports #659

Closed
dbwiddis opened this issue Apr 7, 2023 · 2 comments · Fixed by #661
Closed

[BUG] Backport workflow seems to have broken backports #659

dbwiddis opened this issue Apr 7, 2023 · 2 comments · Fixed by #661
Labels
bug Something isn't working untriaged

Comments

@dbwiddis
Copy link
Member

dbwiddis commented Apr 7, 2023

What is the bug?

After updating to VachaShah/[email protected], 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?

Run VachaShah/[email protected]
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 97d51f426fff22a45faf7e5f 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.

CC: @VachaShah

@dbwiddis dbwiddis added bug Something isn't working untriaged labels Apr 7, 2023
@VachaShah
Copy link

Hi @dbwiddis, I am working on fixing this issue. In the meantime, can you please revert to 2.1.0? Thank you!

@owaiskazi19
Copy link
Member

@dbwiddis #661

@dbwiddis dbwiddis linked a pull request Apr 7, 2023 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working untriaged
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants