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

[PR #1710/8d7550b3 backport][0.20] Fix a uniqueness violation for is_highest #1813

Conversation

patchback[bot]
Copy link

@patchback patchback bot commented Apr 10, 2024

This is a backport of PR #1710 as merged into main (8d7550b).

When syncing content, we need to ignore the upstream status of is_highest.

[noissue]

When syncing content, we need to ignore the upstream status of is_highest.

[noissue]

(cherry picked from commit 8d7550b)
@ggainey
Copy link
Contributor

ggainey commented Apr 10, 2024

Closing - this cherry-pick isn't possible, the model it references doesn't exist in 0.16

@ggainey ggainey reopened this Apr 10, 2024
@ggainey
Copy link
Contributor

ggainey commented Apr 10, 2024

sigh, wrong PR, reopening

@mdellweg mdellweg enabled auto-merge (rebase) April 11, 2024 08:33
Copy link
Member

@mdellweg mdellweg left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

At least this extra lap seems to have make the CI happy.

@mdellweg mdellweg merged commit 1ef67aa into 0.20 Apr 11, 2024
32 checks passed
@mdellweg mdellweg deleted the patchback/backports/0.20/8d7550b3afedf4eb62abdff8b03a197605320392/pr-1710 branch April 11, 2024 08:34
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

Successfully merging this pull request may close these issues.

2 participants