-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
[CT-1475] [Bug] Automatic Backport fails #6217
Comments
@McKnight-42 did you experience something similar with any of the adapters? |
Inof: backport to |
@emmyoop yeah 1.2. and 1.1 both fails with |
More examples in #6405 |
more examples dbt-labs/dbt-bigquery#411 if we are collecting them. |
The most stright forward solution may be to write our own version of the backport so we can be more in control of how it functions and see the actual reason it's failing. |
Is this a new bug in dbt-core?
Current Behavior
We currently had to do some backports to
1.1.latest
,1.2.latest
and1.3.latest
(original PR)The
1.3.latest
backport worked flawlessly.However the
1.1.latest
and the1.2.latest
both failed. When I manually cherry picked the commits I was able to do it without conflict so it's unclear why the cherry picks failed.Additionally, I was told that if the labels are added before the PR has been merged, the backport will not happen. the labels must be added after the merge is complete. Unsure if this is a bug or just how it works but wanted to note it here as well.
Expected Behavior
Backports just work - always!
Steps To Reproduce
See #6204
The text was updated successfully, but these errors were encountered: