Skip to content

Merge v1.17 into v1.18 #1303

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

Merged
merged 1 commit into from
May 10, 2024
Merged

Merge v1.17 into v1.18 #1303

merged 1 commit into from
May 10, 2024

Conversation

mongodb-php-bot
Copy link
Collaborator

Merge new changes from v1.17 into v1.18.

Commits

Resolving conflicts

To resolve any conflicts, check out the temporary branch and run the following command:
git merge v1.18

Ignoring changes

To ignore from the remote branch, first reset the temporary branch to v1.18 and manually merge using the `ours` merge strategy:
git reset --hard v1.18
git merge --strategy=ours v1.17

Then, push the temporary branch to upate the pull request.

@mongodb-php-bot mongodb-php-bot requested a review from a team as a code owner May 10, 2024 17:10
@mongodb-php-bot mongodb-php-bot requested a review from jmikola May 10, 2024 17:10
@jmikola jmikola merged commit 0786f31 into v1.18 May 10, 2024
5 of 6 checks passed
@jmikola jmikola deleted the merge-v1.17-into-v1.18-1715361030131 branch May 10, 2024 17:11
This was referenced May 10, 2024
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