Skip to content

Test #590

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
Feb 10, 2025
Merged

Test #590

merged 1 commit into from
Feb 10, 2025

Conversation

mayaraman19
Copy link
Collaborator

test

Copy link

netlify bot commented Feb 5, 2025

Deploy Preview for docs-cluster-to-cluster-sync ready!

Name Link
🔨 Latest commit 2cf9dc7
🔍 Latest deploy log https://app.netlify.com/sites/docs-cluster-to-cluster-sync/deploys/67a3c7cc44b96500084666ca
😎 Deploy Preview https://deploy-preview-590--docs-cluster-to-cluster-sync.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

@ajhuh-mdb ajhuh-mdb merged commit eebc367 into mongodb:master Feb 10, 2025
4 checks passed
github-actions bot pushed a commit that referenced this pull request Feb 10, 2025
(cherry picked from commit eebc367)
Copy link

The backport to v1.9 failed:

Server Error

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-v1.9 v1.9
# Navigate to the new working tree
cd .worktrees/backport-v1.9
# Create a new branch
git switch --create backport-590-to-v1.9
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 eebc3675b4dbfcd97b6fe0d79b3b4f05816e07a8
# Push it to GitHub
git push --set-upstream origin backport-590-to-v1.9
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-v1.9

Then, create a pull request where the base branch is v1.9 and the compare/head branch is backport-590-to-v1.9.

@github-actions github-actions bot mentioned this pull request Feb 10, 2025
github-actions bot pushed a commit that referenced this pull request Feb 10, 2025
(cherry picked from commit eebc367)
Copy link

The backport to v1.8 failed:

Server Error

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-v1.8 v1.8
# Navigate to the new working tree
cd .worktrees/backport-v1.8
# Create a new branch
git switch --create backport-590-to-v1.8
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 eebc3675b4dbfcd97b6fe0d79b3b4f05816e07a8
# Push it to GitHub
git push --set-upstream origin backport-590-to-v1.8
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-v1.8

Then, create a pull request where the base branch is v1.8 and the compare/head branch is backport-590-to-v1.8.

github-actions bot pushed a commit that referenced this pull request Feb 10, 2025
(cherry picked from commit eebc367)
Copy link

The backport to v1.10 failed:

Server Error

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-v1.10 v1.10
# Navigate to the new working tree
cd .worktrees/backport-v1.10
# Create a new branch
git switch --create backport-590-to-v1.10
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 eebc3675b4dbfcd97b6fe0d79b3b4f05816e07a8
# Push it to GitHub
git push --set-upstream origin backport-590-to-v1.10
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-v1.10

Then, create a pull request where the base branch is v1.10 and the compare/head branch is backport-590-to-v1.10.

This was referenced Feb 10, 2025
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