Skip to content

[PHP] Duplicate Titles - Connect to MongoDB #224

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
Mar 11, 2025

Conversation

rachel-mack
Copy link
Collaborator

@rachel-mack rachel-mack commented Mar 10, 2025

Pull Request Info

PR Reviewing Guidelines

JIRA - https://jira.mongodb.org/browse/DOCSP-48232

Merging the Get Started section into one page, per the new TOC guidelines
Ignoring language-related vale complaints because this is all c+p.

Staging - https://deploy-preview-224--docs-php-library.netlify.app/get-started/

Self-Review Checklist

  • Is this free of any warnings or errors in the RST?
  • Did you run a spell-check?
  • Did you run a grammar-check?
  • Are all the links working?
  • Are the facets and meta keywords accurate?

Copy link

netlify bot commented Mar 10, 2025

Deploy Preview for docs-php-library ready!

Name Link
🔨 Latest commit d8be483
🔍 Latest deploy log https://app.netlify.com/sites/docs-php-library/deploys/67cf39449733680008e2a3d8
😎 Deploy Preview https://deploy-preview-224--docs-php-library.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.

@rachel-mack rachel-mack changed the title [PHP] Duplicate Titles - Connect to MongoDB - PHP [PHP] Duplicate Titles - Connect to MongoDB Mar 10, 2025
Copy link
Collaborator

@jordan-smith721 jordan-smith721 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@rachel-mack rachel-mack merged commit 619e955 into mongodb:master Mar 11, 2025
7 of 8 checks passed
Copy link

The backport to v1.20 failed:

The process '/usr/bin/git' failed with exit code 128

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.20 v1.20
# Navigate to the new working tree
cd .worktrees/backport-v1.20
# Create a new branch
git switch --create backport-224-to-v1.20
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 619e9554fbc1f32c179d3037283737fc766a6b50
# Push it to GitHub
git push --set-upstream origin backport-224-to-v1.20
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-v1.20

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

Copy link

The backport to v1.21 failed:

The process '/usr/bin/git' failed with exit code 128

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.21 v1.21
# Navigate to the new working tree
cd .worktrees/backport-v1.21
# Create a new branch
git switch --create backport-224-to-v1.21
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 619e9554fbc1f32c179d3037283737fc766a6b50
# Push it to GitHub
git push --set-upstream origin backport-224-to-v1.21
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-v1.21

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

Copy link

The backport to v2.0 failed:

The process '/usr/bin/git' failed with exit code 128

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-v2.0 v2.0
# Navigate to the new working tree
cd .worktrees/backport-v2.0
# Create a new branch
git switch --create backport-224-to-v2.0
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 619e9554fbc1f32c179d3037283737fc766a6b50
# Push it to GitHub
git push --set-upstream origin backport-224-to-v2.0
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-v2.0

Then, create a pull request where the base branch is v2.0 and the compare/head branch is backport-224-to-v2.0.

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