Skip to content

Conversation

@shuangela
Copy link
Collaborator

@shuangela shuangela commented Mar 27, 2025

@netlify
Copy link

netlify bot commented Mar 27, 2025

Deploy Preview for docs-csharp ready!

Name Link
🔨 Latest commit 13f2e22
🔍 Latest deploy log https://app.netlify.com/sites/docs-csharp/deploys/67e5bac8873cfa00088cf529
😎 Deploy Preview https://deploy-preview-538--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!

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

@github-actions
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-538-to-v2.30
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 22346ac8f15318219a54f046a7131e792be598ff
# Push it to GitHub
git push --set-upstream origin backport-538-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-538-to-v2.30.

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

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

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

github-actions bot pushed a commit that referenced this pull request Mar 27, 2025
* move sync above async

* add back word

(cherry picked from commit 22346ac)
github-actions bot pushed a commit that referenced this pull request Mar 27, 2025
* move sync above async

* add back word

(cherry picked from commit 22346ac)
github-actions bot pushed a commit that referenced this pull request Mar 27, 2025
* move sync above async

* add back word

(cherry picked from commit 22346ac)
@github-actions
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-538-to-v2.25
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 22346ac8f15318219a54f046a7131e792be598ff
# Push it to GitHub
git push --set-upstream origin backport-538-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-538-to-v2.25.

shuangela added a commit that referenced this pull request Mar 27, 2025
* move sync above async

* add back word

(cherry picked from commit 22346ac)

Co-authored-by: shuangela <[email protected]>
shuangela added a commit that referenced this pull request Mar 27, 2025
* move sync above async

* add back word

(cherry picked from commit 22346ac)

Co-authored-by: shuangela <[email protected]>
@github-actions
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-538-to-v2.26
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 22346ac8f15318219a54f046a7131e792be598ff
# Push it to GitHub
git push --set-upstream origin backport-538-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-538-to-v2.26.

@github-actions
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-538-to-v2.30
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 22346ac8f15318219a54f046a7131e792be598ff
# Push it to GitHub
git push --set-upstream origin backport-538-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-538-to-v2.30.

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

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

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

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

shuangela added a commit that referenced this pull request Mar 27, 2025
* move sync above async

* add back word

(cherry picked from commit 22346ac)

Co-authored-by: shuangela <[email protected]>
mongoKart pushed a commit to mongoKart/docs-csharp that referenced this pull request May 16, 2025
* move sync above async

* add back word
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.

2 participants