-
Notifications
You must be signed in to change notification settings - Fork 9
[Kotlin] Duplicate Titles - Connect to MongoDB #84
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
Conversation
✅ Deploy Preview for docs-kotlin-sync ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
4af1e74
to
5aa8c17
Compare
.. TODO add after output .. tip:: Data Classes | ||
.. | ||
.. To learn more about using data classes to store and retrieve data, | ||
.. see the :ref:`fundamentals-data-classes` guide. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
S: while you are here consider uncommenting this tip and updating the link
5aa8c17
to
6ed5fa3
Compare
The backport to
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-v5.2 v5.2
# Navigate to the new working tree
cd .worktrees/backport-v5.2
# Create a new branch
git switch --create backport-84-to-v5.2
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 ce38b145757ecb000d531421756cf418e89c200e
# Push it to GitHub
git push --set-upstream origin backport-84-to-v5.2
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-v5.2 Then, create a pull request where the |
The backport to
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-v5.1 v5.1
# Navigate to the new working tree
cd .worktrees/backport-v5.1
# Create a new branch
git switch --create backport-84-to-v5.1
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 ce38b145757ecb000d531421756cf418e89c200e
# Push it to GitHub
git push --set-upstream origin backport-84-to-v5.1
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-v5.1 Then, create a pull request where the |
The backport to
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-v5.3 v5.3
# Navigate to the new working tree
cd .worktrees/backport-v5.3
# Create a new branch
git switch --create backport-84-to-v5.3
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 ce38b145757ecb000d531421756cf418e89c200e
# Push it to GitHub
git push --set-upstream origin backport-84-to-v5.3
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-v5.3 Then, create a pull request where the |
Pull Request Info
PR Reviewing Guidelines
JIRA - https://jira.mongodb.org/browse/DOCSP-48233
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 Links
Self-Review Checklist