Skip to content

DOCSP-44897 TOC Relabel #287

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 3 commits into from
Nov 8, 2024
Merged

Conversation

lindseymoore
Copy link
Collaborator

@lindseymoore lindseymoore commented Nov 6, 2024

Pull Request Info

PR Reviewing Guidelines

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

Staging Links

  • fundamentals
  • fundamentals/connection
  • fundamentals/crud
  • fundamentals/crud/read-operations
  • fundamentals/crud/write-operations
  • fundamentals/serialization
  • index
  • upgrade
  • usage-examples
  • Original: https://www.mongodb.com/docs/drivers/csharp/current/

    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?

    Copy link

    netlify bot commented Nov 6, 2024

    Deploy Preview for mongodb-docs-csharp ready!

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

    Copy link
    Collaborator

    @mongoKart mongoKart left a comment

    Choose a reason for hiding this comment

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

    lgtm!

    @lindseymoore lindseymoore merged commit c48dd6e into mongodb:master Nov 8, 2024
    6 checks passed
    Copy link

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

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

    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-287-to-v2.29
    # Cherry-pick the merged commit of this pull request and resolve the conflicts
    git cherry-pick -x --mainline 1 c48dd6efc513091ed27c9a8855dca8aa6d16d88d
    # Push it to GitHub
    git push --set-upstream origin backport-287-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-287-to-v2.29.

    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-287-to-v2.25
    # Cherry-pick the merged commit of this pull request and resolve the conflicts
    git cherry-pick -x --mainline 1 c48dd6efc513091ed27c9a8855dca8aa6d16d88d
    # Push it to GitHub
    git push --set-upstream origin backport-287-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-287-to-v2.25.

    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-287-to-v2.28
    # Cherry-pick the merged commit of this pull request and resolve the conflicts
    git cherry-pick -x --mainline 1 c48dd6efc513091ed27c9a8855dca8aa6d16d88d
    # Push it to GitHub
    git push --set-upstream origin backport-287-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-287-to-v2.28.

    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-287-to-v2.26
    # Cherry-pick the merged commit of this pull request and resolve the conflicts
    git cherry-pick -x --mainline 1 c48dd6efc513091ed27c9a8855dca8aa6d16d88d
    # Push it to GitHub
    git push --set-upstream origin backport-287-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-287-to-v2.26.

    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-287-to-v2.27
    # Cherry-pick the merged commit of this pull request and resolve the conflicts
    git cherry-pick -x --mainline 1 c48dd6efc513091ed27c9a8855dca8aa6d16d88d
    # Push it to GitHub
    git push --set-upstream origin backport-287-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-287-to-v2.27.

    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-287-to-v2.24
    # Cherry-pick the merged commit of this pull request and resolve the conflicts
    git cherry-pick -x --mainline 1 c48dd6efc513091ed27c9a8855dca8aa6d16d88d
    # Push it to GitHub
    git push --set-upstream origin backport-287-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-287-to-v2.24.

    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-287-to-v2.22
    # Cherry-pick the merged commit of this pull request and resolve the conflicts
    git cherry-pick -x --mainline 1 c48dd6efc513091ed27c9a8855dca8aa6d16d88d
    # Push it to GitHub
    git push --set-upstream origin backport-287-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-287-to-v2.22.

    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-287-to-v2.23
    # Cherry-pick the merged commit of this pull request and resolve the conflicts
    git cherry-pick -x --mainline 1 c48dd6efc513091ed27c9a8855dca8aa6d16d88d
    # Push it to GitHub
    git push --set-upstream origin backport-287-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-287-to-v2.23.

    lindseymoore added a commit to lindseymoore/docs-csharp that referenced this pull request Nov 19, 2024
    * DOCSP-44897 TOC Relabel
    
    * encryption rendering issue
    
    * encryption still not rendering
    
    (cherry picked from commit c48dd6e)
    lindseymoore added a commit that referenced this pull request Nov 19, 2024
    * DOCSP-44897 TOC Relabel (#287)
    
    * DOCSP-44897 TOC Relabel
    
    * encryption rendering issue
    
    * encryption still not rendering
    
    (cherry picked from commit c48dd6e)
    
    * edit
    
    * limit results
    
    * query results
    lindseymoore added a commit to lindseymoore/docs-csharp that referenced this pull request Nov 19, 2024
    * DOCSP-44897 TOC Relabel
    
    * encryption rendering issue
    
    * encryption still not rendering
    
    (cherry picked from commit c48dd6e)
    lindseymoore added a commit that referenced this pull request Nov 19, 2024
    * DOCSP-44897 TOC Relabel (#287)
    
    * DOCSP-44897 TOC Relabel
    
    * encryption rendering issue
    
    * encryption still not rendering
    
    (cherry picked from commit c48dd6e)
    
    * read changes
    github-actions bot pushed a commit that referenced this pull request Nov 19, 2024
    * DOCSP-44897 TOC Relabel (#287)
    
    * DOCSP-44897 TOC Relabel
    
    * encryption rendering issue
    
    * encryption still not rendering
    
    (cherry picked from commit c48dd6e)
    
    * read changes
    
    (cherry picked from commit e66022f)
    github-actions bot pushed a commit that referenced this pull request Nov 19, 2024
    * DOCSP-44897 TOC Relabel (#287)
    
    * DOCSP-44897 TOC Relabel
    
    * encryption rendering issue
    
    * encryption still not rendering
    
    (cherry picked from commit c48dd6e)
    
    * read changes
    
    (cherry picked from commit e66022f)
    github-actions bot pushed a commit that referenced this pull request Nov 19, 2024
    * DOCSP-44897 TOC Relabel (#287)
    
    * DOCSP-44897 TOC Relabel
    
    * encryption rendering issue
    
    * encryption still not rendering
    
    (cherry picked from commit c48dd6e)
    
    * read changes
    
    (cherry picked from commit e66022f)
    github-actions bot pushed a commit that referenced this pull request Nov 19, 2024
    * DOCSP-44897 TOC Relabel (#287)
    
    * DOCSP-44897 TOC Relabel
    
    * encryption rendering issue
    
    * encryption still not rendering
    
    (cherry picked from commit c48dd6e)
    
    * read changes
    
    (cherry picked from commit e66022f)
    github-actions bot pushed a commit that referenced this pull request Nov 19, 2024
    * DOCSP-44897 TOC Relabel (#287)
    
    * DOCSP-44897 TOC Relabel
    
    * encryption rendering issue
    
    * encryption still not rendering
    
    (cherry picked from commit c48dd6e)
    
    * read changes
    
    (cherry picked from commit e66022f)
    github-actions bot pushed a commit that referenced this pull request Nov 19, 2024
    * DOCSP-44897 TOC Relabel (#287)
    
    * DOCSP-44897 TOC Relabel
    
    * encryption rendering issue
    
    * encryption still not rendering
    
    (cherry picked from commit c48dd6e)
    
    * read changes
    
    (cherry picked from commit e66022f)
    github-actions bot pushed a commit that referenced this pull request Nov 19, 2024
    * DOCSP-44897 TOC Relabel (#287)
    
    * DOCSP-44897 TOC Relabel
    
    * encryption rendering issue
    
    * encryption still not rendering
    
    (cherry picked from commit c48dd6e)
    
    * read changes
    
    (cherry picked from commit e66022f)
    lindseymoore added a commit that referenced this pull request Nov 19, 2024
    * DOCSP-44897 TOC Relabel (#287)
    
    * DOCSP-44897 TOC Relabel
    
    * encryption rendering issue
    
    * encryption still not rendering
    
    (cherry picked from commit c48dd6e)
    
    * read changes
    
    (cherry picked from commit e66022f)
    
    Co-authored-by: lindseymoore <[email protected]>
    lindseymoore added a commit that referenced this pull request Nov 19, 2024
    * DOCSP-44897 TOC Relabel (#287)
    
    * DOCSP-44897 TOC Relabel
    
    * encryption rendering issue
    
    * encryption still not rendering
    
    (cherry picked from commit c48dd6e)
    
    * read changes
    
    (cherry picked from commit e66022f)
    
    Co-authored-by: lindseymoore <[email protected]>
    lindseymoore added a commit that referenced this pull request Nov 19, 2024
    * DOCSP-44897 TOC Relabel (#287)
    
    * DOCSP-44897 TOC Relabel
    
    * encryption rendering issue
    
    * encryption still not rendering
    
    (cherry picked from commit c48dd6e)
    
    * read changes
    
    (cherry picked from commit e66022f)
    
    Co-authored-by: lindseymoore <[email protected]>
    lindseymoore added a commit that referenced this pull request Nov 19, 2024
    * DOCSP-44897 TOC Relabel (#287)
    
    * DOCSP-44897 TOC Relabel
    
    * encryption rendering issue
    
    * encryption still not rendering
    
    (cherry picked from commit c48dd6e)
    
    * read changes
    
    (cherry picked from commit e66022f)
    
    Co-authored-by: lindseymoore <[email protected]>
    lindseymoore added a commit that referenced this pull request Nov 19, 2024
    * DOCSP-44897 TOC Relabel (#287)
    
    * DOCSP-44897 TOC Relabel
    
    * encryption rendering issue
    
    * encryption still not rendering
    
    (cherry picked from commit c48dd6e)
    
    * read changes
    
    (cherry picked from commit e66022f)
    
    Co-authored-by: lindseymoore <[email protected]>
    lindseymoore added a commit that referenced this pull request Nov 19, 2024
    * DOCSP-44897 TOC Relabel (#287)
    
    * DOCSP-44897 TOC Relabel
    
    * encryption rendering issue
    
    * encryption still not rendering
    
    (cherry picked from commit c48dd6e)
    
    * read changes
    
    (cherry picked from commit e66022f)
    
    Co-authored-by: lindseymoore <[email protected]>
    lindseymoore added a commit that referenced this pull request Nov 19, 2024
    * DOCSP-44897 TOC Relabel (#287)
    
    * DOCSP-44897 TOC Relabel
    
    * encryption rendering issue
    
    * encryption still not rendering
    
    (cherry picked from commit c48dd6e)
    
    * read changes
    
    (cherry picked from commit e66022f)
    
    Co-authored-by: lindseymoore <[email protected]>
    lindseymoore added a commit to lindseymoore/docs-csharp that referenced this pull request Nov 19, 2024
    * DOCSP-44897 TOC Relabel (mongodb#287)
    
    * DOCSP-44897 TOC Relabel
    
    * encryption rendering issue
    
    * encryption still not rendering
    
    (cherry picked from commit c48dd6e)
    
    * read changes
    
    (cherry picked from commit e66022f)
    lindseymoore added a commit that referenced this pull request Nov 19, 2024
    #319)
    
    * [Backport v2.29] DOCSP-44897 TOC Relabel (#287) (#311)
    
    * DOCSP-44897 TOC Relabel (#287)
    
    * DOCSP-44897 TOC Relabel
    
    * encryption rendering issue
    
    * encryption still not rendering
    
    (cherry picked from commit c48dd6e)
    
    * read changes
    
    (cherry picked from commit e66022f)
    
    * revert api link
    mongoKart pushed a commit to mongoKart/docs-csharp that referenced this pull request May 16, 2025
    * DOCSP-44897 TOC Relabel
    
    * encryption rendering issue
    
    * encryption still not rendering
    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