Skip to content

Merge v2.0 into v2.1 #1708

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

Closed
wants to merge 3 commits into from
Closed

Conversation

mongodb-php-bot
Copy link
Collaborator

Merge new changes from v2.0 into v2.1.

Commits

Resolving conflicts

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

Ignoring changes

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

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

alcaeus and others added 3 commits May 26, 2025 10:43
* Use assume_role command before accessing secrets for atlas-data-lake tests

* Increase task timeout to 30 minutes

* Include AWS expansions when pulling mongohoused image
@mongodb-php-bot mongodb-php-bot requested a review from a team as a code owner May 26, 2025 13:28
@mongodb-php-bot mongodb-php-bot requested a review from alcaeus May 26, 2025 13:28
@mongodb-php-bot mongodb-php-bot enabled auto-merge May 26, 2025 13:28
@alcaeus
Copy link
Member

alcaeus commented May 26, 2025

Closing this to stop chasing builds - there is an other merge-up PR coming once #1709 is merged.

@alcaeus alcaeus closed this May 26, 2025
auto-merge was automatically disabled May 26, 2025 13:45

Pull request was closed

@alcaeus alcaeus deleted the merge-v2.0-into-v2.1-1748266101496 branch May 26, 2025 13:45
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.

2 participants