Skip to content

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

Merged
merged 39 commits into from
Nov 27, 2024
Merged

DOCSP-39980 - GridFS #289

merged 39 commits into from
Nov 27, 2024

Conversation

mongoKart
Copy link
Collaborator

@mongoKart mongoKart commented Nov 12, 2024

Pull Request Info

PR Reviewing Guidelines

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

Staging Links

  • fundamentals/gridfs
  • fundamentals
  • fundamentals/crud/write-operations/insert
  • 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?

    mongoKart and others added 21 commits October 17, 2024 08:37
    Co-authored-by: Jordan Smith <[email protected]>
    (cherry picked from commit 1d75584)
    Co-authored-by: your proper name <your github email>
    (cherry picked from commit 42bd42f)
    (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)
    Co-authored-by: Rea Rustagi <[email protected]>
    (cherry picked from commit 12fc8ef)
    
    Co-authored-by: Mike Woofter <[email protected]>
    Copy link

    netlify bot commented Nov 12, 2024

    Deploy Preview for mongodb-docs-csharp ready!

    Name Link
    🔨 Latest commit ef4bc97
    🔍 Latest deploy log https://app.netlify.com/sites/mongodb-docs-csharp/deploys/674751a9b1bc8a0008ec2154
    😎 Deploy Preview https://deploy-preview-289--mongodb-docs-csharp.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.

    @mongoKart mongoKart merged commit 86eb2be into mongodb:master Nov 27, 2024
    5 of 6 checks passed
    @mongoKart mongoKart deleted the docsp-39980-gridfs branch November 27, 2024 17:07
    github-actions bot pushed a commit that referenced this pull request Nov 27, 2024
    (cherry picked from commit 86eb2be)
    Copy link

    The backport to v2.30 failed:

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

    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 base branch is v2.30 and the compare/head branch is backport-289-to-v2.30.

    Copy link

    The backport to v2.29 failed:

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

    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 base branch is v2.29 and the compare/head branch is backport-289-to-v2.29.

    Copy link

    The backport to v2.28 failed:

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

    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 base branch is v2.28 and the compare/head branch is backport-289-to-v2.28.

    Copy link

    The backport to v2.27 failed:

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

    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 base branch is v2.27 and the compare/head branch is backport-289-to-v2.27.

    Copy link

    The backport to v2.26 failed:

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

    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 base branch is v2.26 and the compare/head branch is backport-289-to-v2.26.

    Copy link

    The backport to v2.25 failed:

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

    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 base branch is v2.25 and the compare/head branch is backport-289-to-v2.25.

    Copy link

    The backport to v2.24 failed:

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

    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 base branch is v2.24 and the compare/head branch is backport-289-to-v2.24.

    Copy link

    The backport to v2.23 failed:

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

    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 base branch is v2.23 and the compare/head branch is backport-289-to-v2.23.

    Copy link

    The backport to v2.22 failed:

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

    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 base branch is v2.22 and the compare/head branch is backport-289-to-v2.22.

    mongoKart pushed a commit that referenced this pull request Nov 27, 2024
    (cherry picked from commit 86eb2be)
    mongoKart added a commit to mongoKart/docs-csharp that referenced this pull request Nov 27, 2024
    (cherry picked from commit 86eb2be)
    mongoKart added a commit that referenced this pull request Nov 27, 2024
    (cherry picked from commit 86eb2be)
    mongoKart added a commit to mongoKart/docs-csharp that referenced this pull request Nov 27, 2024
    (cherry picked from commit 86eb2be)
    (cherry picked from commit af51528)
    mongoKart added a commit that referenced this pull request Nov 27, 2024
    (cherry picked from commit 86eb2be)
    (cherry picked from commit af51528)
    mongoKart added a commit that referenced this pull request Nov 27, 2024
    (cherry picked from commit 86eb2be)
    (cherry picked from commit af51528)
    mongoKart added a commit that referenced this pull request Nov 27, 2024
    (cherry picked from commit 86eb2be)
    (cherry picked from commit af51528)
    (cherry picked from commit 9ef610d)
    mongoKart added a commit that referenced this pull request Nov 27, 2024
    (cherry picked from commit 86eb2be)
    (cherry picked from commit af51528)
    (cherry picked from commit 9ef610d)
    mongoKart added a commit that referenced this pull request Nov 27, 2024
    (cherry picked from commit 86eb2be)
    (cherry picked from commit af51528)
    (cherry picked from commit 9ef610d)
    mongoKart added a commit that referenced this pull request Nov 27, 2024
    (cherry picked from commit 86eb2be)
    (cherry picked from commit af51528)
    (cherry picked from commit 9ef610d)
    mongoKart added a commit that referenced this pull request Nov 27, 2024
    (cherry picked from commit 86eb2be)
    (cherry picked from commit af51528)
    (cherry picked from commit 9ef610d)
    mongoKart added a commit to mongoKart/docs-csharp that referenced this pull request May 16, 2025
    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.

    7 participants