DOCSP-44897 TOC relabel V3.0 #296
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* DOCSP-44897 TOC Relabel * encryption rendering issue * encryption still not rendering (cherry picked from commit c48dd6e)
✅ Deploy Preview for mongodb-docs-csharp ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
|
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-296-to-v2.30
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 8d434f393b322762ae47dfdd12f59069fa873d3c
# Push it to GitHub
git push --set-upstream origin backport-296-to-v2.30
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-v2.30Then, 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-296-to-v2.29
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 8d434f393b322762ae47dfdd12f59069fa873d3c
# Push it to GitHub
git push --set-upstream origin backport-296-to-v2.29
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-v2.29Then, 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-296-to-v2.24
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 8d434f393b322762ae47dfdd12f59069fa873d3c
# Push it to GitHub
git push --set-upstream origin backport-296-to-v2.24
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-v2.24Then, 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-296-to-v2.25
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 8d434f393b322762ae47dfdd12f59069fa873d3c
# Push it to GitHub
git push --set-upstream origin backport-296-to-v2.25
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-v2.25Then, 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-296-to-v2.27
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 8d434f393b322762ae47dfdd12f59069fa873d3c
# Push it to GitHub
git push --set-upstream origin backport-296-to-v2.27
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-v2.27Then, 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-296-to-v2.22
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 8d434f393b322762ae47dfdd12f59069fa873d3c
# Push it to GitHub
git push --set-upstream origin backport-296-to-v2.22
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-v2.22Then, 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-296-to-v2.26
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 8d434f393b322762ae47dfdd12f59069fa873d3c
# Push it to GitHub
git push --set-upstream origin backport-296-to-v2.26
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-v2.26Then, 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-296-to-v2.23
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 8d434f393b322762ae47dfdd12f59069fa873d3c
# Push it to GitHub
git push --set-upstream origin backport-296-to-v2.23
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-v2.23Then, create a pull request where the |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Pull Request Info
PR Reviewing Guidelines
JIRA - https://jira.mongodb.org/browse/DOCSP-44897
Staging Links
Self-Review Checklist