Skip to content
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

Merge release/dev17.11 to main #10643

Merged
merged 2 commits into from
Jul 18, 2024
Merged

Conversation

dotnet-bot
Copy link
Contributor

This is an automatically generated pull request from release/dev17.11 into main.

Once all conflicts are resolved and all the tests pass, you are free to merge the pull request. 🐯

Troubleshooting conflicts

Identify authors of changes which introduced merge conflicts

Scroll to the bottom, then for each file containing conflicts copy its path into the following searches:

Usually the most recent change to a file between the two branches is considered to have introduced the conflicts, but sometimes it will be necessary to look for the conflicting lines and check the blame in each branch. Generally the author whose change introduced the conflicts should pull down this PR, fix the conflicts locally, then push up a commit resolving the conflicts.

Resolve merge conflicts using your local repo

Sometimes merge conflicts may be present on GitHub but merging locally will work without conflicts. This is due to differences between the merge algorithm used in local git versus the one used by GitHub.

git fetch --all
git checkout -t upstream/merges/release/dev17.11-to-main
git reset --hard upstream/main
git merge upstream/release/dev17.11
# Fix merge conflicts
git commit
git push upstream merges/release/dev17.11-to-main --force

DustinCampbell and others added 2 commits July 16, 2024 17:42
This was simply a mistake on my part. We should not assume that code is unreachable when it is reached because an OperationCanceledException is caught.
This pull request cherry-picks b8f14d3
to `release/dev17.11`
@dotnet-bot dotnet-bot requested a review from a team as a code owner July 18, 2024 09:04
@dotnet-bot dotnet-bot added area-infrastructure auto-merge Squash merge once all PR checks are complete and reviewers have approved labels Jul 18, 2024
@dotnet-bot dotnet-bot merged commit 5d75e5e into main Jul 18, 2024
12 checks passed
@dotnet-bot dotnet-bot deleted the merges/release/dev17.11-to-main branch July 18, 2024 09:29
@dotnet-policy-service dotnet-policy-service bot added this to the Next milestone Jul 18, 2024
@RikkiGibson RikkiGibson modified the milestones: Next, 17.12 Preview 1 Jul 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-infrastructure auto-merge Squash merge once all PR checks are complete and reviewers have approved
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants