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

Merge release/2.1 back to main after releasing v2.1.1 #17066

Merged
merged 7 commits into from
Nov 25, 2024
Merged

Conversation

MikeAlhayek
Copy link
Member

No description provided.

Copy link
Contributor

This pull request has merge conflicts. Please resolve those before requesting a review.

@MikeAlhayek
Copy link
Member Author

@sebastienros please merge this PR using "Create Merge Commit". After merging it, please restore this branch.

@sebastienros
Copy link
Member

What is nice is that we can create this PR, review and do changes, but them merge manually to create a merge commit and GH will assign/close this PR. So no need to change the GH settings.

Copy link
Contributor

This pull request has merge conflicts. Please resolve those before requesting a review.

@sebastienros sebastienros merged commit b0d9465 into main Nov 25, 2024
18 checks passed
@sebastienros sebastienros deleted the release/2.1 branch November 25, 2024 20:08
@sebastienros sebastienros restored the release/2.1 branch November 25, 2024 20:09
@sebastienros
Copy link
Member

And, just so there is some written trace for our future selves, we should not resolve the conflicts in GH PRs because it merges the target branch (main) into the working one (release/2.1) and that's a problem.

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

Successfully merging this pull request may close these issues.

2 participants