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 2.17.x up into 2.18.x #11201

Merged
merged 5 commits into from
Jan 31, 2024
Merged

Merge 2.17.x up into 2.18.x #11201

merged 5 commits into from
Jan 31, 2024

Conversation

mpdude
Copy link
Contributor

@mpdude mpdude commented Jan 31, 2024

@mpdude mpdude changed the title Merge up 2.17.x into 2.18.x Merge 2.17.x up into 2.18.x Jan 31, 2024
@mpdude mpdude requested review from greg0ire and derrabus January 31, 2024 14:44
@greg0ire greg0ire merged commit f2176a9 into doctrine:2.18.x Jan 31, 2024
56 checks passed
@greg0ire
Copy link
Member

Thanks @mpdude !

@mpdude mpdude deleted the merge-up-217-218 branch January 31, 2024 16:30
@mpdude
Copy link
Contributor Author

mpdude commented Jan 31, 2024

Merging 2.18 into 3.0 seems way more complex with lots of conflicts. How to best approach that?

@greg0ire
Copy link
Member

greg0ire commented Jan 31, 2024

You may cherry-pick your commit so that you don't have to deal with the merge up. In general, to deal with big merges up, the best is to merge a commit that is not the latest 2.18, but something between the last merge up point and now. https://github.com/mhagger/git-imerge can help with automating that.

@greg0ire
Copy link
Member

greg0ire commented Jan 31, 2024

That being said, the diff between those branches seems small, so it's a bit suprising that you're having conflicts 🤔 : 3.0.x...2.18.x

Have you made sure your copy of 3.0.x is up to date?

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.

3 participants