Skip to content

Conversation

@dotnet-bot
Copy link
Contributor

This is an automatically generated pull request from release/dev17.13 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.13-to-main
git reset --hard upstream/main
git merge upstream/release/dev17.13
# Fix merge conflicts
git commit
git push upstream merges/release/dev17.13-to-main --force

This reverts commit 76cd92a, reversing
changes made to a37ee12.
Revert "Some random clean up and improvements (#11095) for dev17.13
@dotnet-bot dotnet-bot requested review from a team as code owners November 6, 2024 06:02
@dotnet-bot dotnet-bot added area-infrastructure auto-merge Squash merge once all PR checks are complete and reviewers have approved labels Nov 6, 2024
@dotnet-bot dotnet-bot enabled auto-merge November 6, 2024 06:02
@dotnet-bot dotnet-bot merged commit 6e796fe into main Nov 6, 2024
12 checks passed
@dotnet-bot dotnet-bot deleted the merges/release/dev17.13-to-main branch November 6, 2024 06:34
@dotnet-policy-service dotnet-policy-service bot added this to the Next milestone Nov 6, 2024
@jjonescz jjonescz modified the milestones: Next, 17.13 P2 Nov 25, 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