-
Notifications
You must be signed in to change notification settings - Fork 20
DOCSP-47173 - Remove FAQs #175
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-pymongo ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
source/faq.txt
Outdated
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.
This empty page will not be in the final merge; it's here to quickly show all the FAQs (including those that were removed).
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.
Nice work! Just a couple small things but otherwise LGTM
source/compatibility.txt
Outdated
@@ -50,5 +50,5 @@ The first column lists the driver version. | |||
|
|||
.. include:: /includes/language-compatibility-table-pymongo.rst | |||
|
|||
For more information on how to read the compatibility tables, see our guide on | |||
For more information about how to read the compatibility tables, see |
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.
I think this should be moved up above the "Python 2" header so that it's closer to the actual table (since the Python 2 section doesn't have a table in it)
Co-authored-by: Jordan Smith <[email protected]>
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-v4.10 v4.10
# Navigate to the new working tree
cd .worktrees/backport-v4.10
# Create a new branch
git switch --create backport-175-to-v4.10
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 39799a54608d06fc65c0ba7a05bd167c62864e3e
# Push it to GitHub
git push --set-upstream origin backport-175-to-v4.10
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-v4.10 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-v4.9 v4.9
# Navigate to the new working tree
cd .worktrees/backport-v4.9
# Create a new branch
git switch --create backport-175-to-v4.9
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 39799a54608d06fc65c0ba7a05bd167c62864e3e
# Push it to GitHub
git push --set-upstream origin backport-175-to-v4.9
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-v4.9 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-v4.8 v4.8
# Navigate to the new working tree
cd .worktrees/backport-v4.8
# Create a new branch
git switch --create backport-175-to-v4.8
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 39799a54608d06fc65c0ba7a05bd167c62864e3e
# Push it to GitHub
git push --set-upstream origin backport-175-to-v4.8
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-v4.8 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-v4.7 v4.7
# Navigate to the new working tree
cd .worktrees/backport-v4.7
# Create a new branch
git switch --create backport-175-to-v4.7
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 39799a54608d06fc65c0ba7a05bd167c62864e3e
# Push it to GitHub
git push --set-upstream origin backport-175-to-v4.7
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-v4.7 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-v4.11 v4.11
# Navigate to the new working tree
cd .worktrees/backport-v4.11
# Create a new branch
git switch --create backport-175-to-v4.11
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 39799a54608d06fc65c0ba7a05bd167c62864e3e
# Push it to GitHub
git push --set-upstream origin backport-175-to-v4.11
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-v4.11 Then, create a pull request where the |
Co-authored-by: Jordan Smith <[email protected]> (cherry picked from commit 39799a5)
Co-authored-by: Jordan Smith <[email protected]> (cherry picked from commit 39799a5) (cherry picked from commit 4281bb3)
Co-authored-by: Jordan Smith <[email protected]> (cherry picked from commit 39799a5) (cherry picked from commit 4281bb3) (cherry picked from commit 5752f45)
Co-authored-by: Jordan Smith <[email protected]> (cherry picked from commit 39799a5) (cherry picked from commit 4281bb3) (cherry picked from commit 5752f45)
Co-authored-by: Jordan Smith <[email protected]> (cherry picked from commit 39799a5) (cherry picked from commit 4281bb3) (cherry picked from commit 5752f45)
This PR moves the FAQs to the pages that contain the relevant content. A few that pertain strictly to Python, rather than to PyMongo, were deleted.
Pull Request Info
PR Reviewing Guidelines
JIRA - https://jira.mongodb.org/browse/DOCSP-47173
Staging Links
Self-Review Checklist