Skip to content

Merge v1.17 into v1.18 #1315

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 2 commits into from
May 22, 2024
Merged

Merge v1.17 into v1.18 #1315

merged 2 commits into from
May 22, 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 21, 2024 20:46
@mongodb-php-bot mongodb-php-bot requested a review from jmikola May 21, 2024 20:46
@jmikola
Copy link
Member

jmikola commented May 22, 2024

In this Slack thread, @GromNaN mentioned that #1308 split Rector into its own CI job. I'm not sure why it's still included in the Psalm job above.

Does this require a manual PR where I create a branch from v1.18, merge v1.17 into that, and then open a PR to merge into v1.18?

@alcaeus alcaeus merged commit ae5a86f into v1.18 May 22, 2024
17 of 18 checks passed
@alcaeus alcaeus deleted the merge-v1.17-into-v1.18-1716324368115 branch May 22, 2024 07:26
This was referenced May 22, 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.

4 participants