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

Backport function picks up individual commits instead of using squash/merge commit #110

Open
karenzone opened this issue Jun 9, 2020 · 0 comments
Assignees

Comments

@karenzone
Copy link

The @jarvis backport command didn't work as I expected.
Disclaimer: Could be user error or that I have an inaccurate mental model.

Case: elastic/logstash#11715
I got my local copy in a questionable state, and so I squash/merged into master from github.: elastic/logstash@34ee17b

I did: @jarvis backport https://github.com/elastic/logstash/pull/11715 7.x 7.8 7.7
I expected the single squash/merged commit to be backported.
Instead, the commits were backported individually.

Is Jarvis expecting the commit instead of the PR perhaps?
@jarvis backport 34ee17b0bfc89816f1d968bae07f2c2f7e081b14 7.x is 7.8 7.7

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants