-
Notifications
You must be signed in to change notification settings - Fork 25
DOCSP-39980 - GridFS #289
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
DOCSP-39980 - GridFS #289
Conversation
Co-authored-by: Jordan Smith <[email protected]> (cherry picked from commit 1d75584)
(cherry picked from commit dd333de)
Co-authored-by: your proper name <your github email>
(cherry picked from commit 42bd42f)
(cherry picked from commit be18c24)
(cherry picked from commit cd5c1b5) Co-authored-by: Mike Woofter <[email protected]>
(cherry picked from commit 4409e9e) Co-authored-by: Mike Woofter <[email protected]>
* changing code + checkpint * very preliminary first draft * correct code block * code blocks * and and or * xor, not, and other small tweaks * changing variable type in linq.cs * never mind * back to double * addressing basic comments * move code to include * io code block * reworking first sentence * bullet list * bullet list pt 2 * bullet list pt 3 * feedback * nits * change example * correction * snake case * refining note * vale (cherry picked from commit a1b1f4c)
(cherry picked from commit 69a08d0)
Co-authored-by: Rea Rustagi <[email protected]> (cherry picked from commit 12fc8ef) Co-authored-by: Mike Woofter <[email protected]>
(cherry picked from commit ab943f9)
(cherry picked from commit 051e6ca)
✅ Deploy Preview for mongodb-docs-csharp ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
(cherry picked from commit 86eb2be)
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-v2.30 v2.30
# Navigate to the new working tree
cd .worktrees/backport-v2.30
# Create a new branch
git switch --create backport-289-to-v2.30
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 86eb2be7b033653e9ebbcdb0453c31f6ad26beb3
# Push it to GitHub
git push --set-upstream origin backport-289-to-v2.30
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-v2.30 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-v2.29 v2.29
# Navigate to the new working tree
cd .worktrees/backport-v2.29
# Create a new branch
git switch --create backport-289-to-v2.29
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 86eb2be7b033653e9ebbcdb0453c31f6ad26beb3
# Push it to GitHub
git push --set-upstream origin backport-289-to-v2.29
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-v2.29 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-v2.28 v2.28
# Navigate to the new working tree
cd .worktrees/backport-v2.28
# Create a new branch
git switch --create backport-289-to-v2.28
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 86eb2be7b033653e9ebbcdb0453c31f6ad26beb3
# Push it to GitHub
git push --set-upstream origin backport-289-to-v2.28
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-v2.28 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-v2.27 v2.27
# Navigate to the new working tree
cd .worktrees/backport-v2.27
# Create a new branch
git switch --create backport-289-to-v2.27
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 86eb2be7b033653e9ebbcdb0453c31f6ad26beb3
# Push it to GitHub
git push --set-upstream origin backport-289-to-v2.27
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-v2.27 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-v2.26 v2.26
# Navigate to the new working tree
cd .worktrees/backport-v2.26
# Create a new branch
git switch --create backport-289-to-v2.26
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 86eb2be7b033653e9ebbcdb0453c31f6ad26beb3
# Push it to GitHub
git push --set-upstream origin backport-289-to-v2.26
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-v2.26 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-v2.25 v2.25
# Navigate to the new working tree
cd .worktrees/backport-v2.25
# Create a new branch
git switch --create backport-289-to-v2.25
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 86eb2be7b033653e9ebbcdb0453c31f6ad26beb3
# Push it to GitHub
git push --set-upstream origin backport-289-to-v2.25
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-v2.25 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-v2.24 v2.24
# Navigate to the new working tree
cd .worktrees/backport-v2.24
# Create a new branch
git switch --create backport-289-to-v2.24
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 86eb2be7b033653e9ebbcdb0453c31f6ad26beb3
# Push it to GitHub
git push --set-upstream origin backport-289-to-v2.24
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-v2.24 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-v2.23 v2.23
# Navigate to the new working tree
cd .worktrees/backport-v2.23
# Create a new branch
git switch --create backport-289-to-v2.23
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 86eb2be7b033653e9ebbcdb0453c31f6ad26beb3
# Push it to GitHub
git push --set-upstream origin backport-289-to-v2.23
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-v2.23 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-v2.22 v2.22
# Navigate to the new working tree
cd .worktrees/backport-v2.22
# Create a new branch
git switch --create backport-289-to-v2.22
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 86eb2be7b033653e9ebbcdb0453c31f6ad26beb3
# Push it to GitHub
git push --set-upstream origin backport-289-to-v2.22
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-v2.22 Then, create a pull request where the |
(cherry picked from commit 86eb2be)
Pull Request Info
PR Reviewing Guidelines
JIRA - https://jira.mongodb.org/browse/DOCSP-39980
Staging Links
Self-Review Checklist