Skip to content

Conversation

@mongoKart
Copy link
Collaborator

Pull Request Info

PR Reviewing Guidelines

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

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?

@netlify
Copy link

netlify bot commented Nov 1, 2024

Deploy Preview for docs-entity-framework ready!

Name Link
🔨 Latest commit 588bdf3
🔍 Latest deploy log https://app.netlify.com/sites/docs-entity-framework/deploys/672511c8f4b1c800086b7c29
😎 Deploy Preview https://deploy-preview-39--docs-entity-framework.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.

Copy link
Collaborator

@lindseymoore lindseymoore left a comment

Choose a reason for hiding this comment

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

LGTM!

@mongoKart mongoKart merged commit a993354 into mongodb:master Nov 4, 2024
7 checks passed
@mongoKart mongoKart deleted the docsp-44898-toc-labels branch November 4, 2024 16:11
@github-actions
Copy link

github-actions bot commented Nov 4, 2024

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

Then, create a pull request where the base branch is v8.1 and the compare/head branch is backport-39-to-v8.1.

@github-actions
Copy link

github-actions bot commented Nov 4, 2024

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

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

@github-actions
Copy link

github-actions bot commented Nov 4, 2024

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

Then, create a pull request where the base branch is v8.2 and the compare/head branch is backport-39-to-v8.2.

@mongoKart mongoKart restored the docsp-44898-toc-labels branch November 4, 2024 16:17
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.

3 participants