-
Notifications
You must be signed in to change notification settings - Fork 889
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
Issue 6202 #6224
base: master
Are you sure you want to change the base?
Issue 6202 #6224
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's add a comment to the code and reduce the test case down to the minimum configs needed to reproduce the issue.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just a minor nit and then I think we're good to go. Also, can you please squash all these commits and then rebase on the latest master. The team strongly discourages merge commits in PRs.
3ed4150
to
83af25f
Compare
…-2024-06-24 subtree-push 2024-06-24 Merge commit from master
Apologies, was trying to squash the recent merge commit and accidentally reset the branch. This reopens the PR. |
The git history seems off to me. I think you might have squashed too many commits or grabbed the wrong commit message somehow? |
This closes #6202 .