Skip to content

Merge release/dev16.10 to release/dev16.11#53676

Merged
457 commits merged intorelease/dev16.11from
merges/release/dev16.10-to-release/dev16.11
May 25, 2021
Merged

Merge release/dev16.10 to release/dev16.11#53676
457 commits merged intorelease/dev16.11from
merges/release/dev16.10-to-release/dev16.11

Conversation

@dotnet-bot
Copy link
Collaborator

This is an automatically generated pull request from release/dev16.10 into release/dev16.11.

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 merges/release/dev16.10-to-release/dev16.11
git reset --hard upstream/release/dev16.11
git merge upstream/release/dev16.10
# Fix merge conflicts
git commit
git push upstream merges/release/dev16.10-to-release/dev16.11 --force

allisonchou and others added 30 commits March 17, 2021 16:47
dibarbet and others added 15 commits April 30, 2021 10:38
…ase/dev16.10-vs-deps

Merge release/dev16.10 to release/dev16.10-vs-deps
…ase/dev16.10-vs-deps

Merge release/dev16.10 to release/dev16.10-vs-deps
…ase/dev16.10-vs-deps

Merge release/dev16.10 to release/dev16.10-vs-deps
…ase/dev16.10-vs-deps

Merge release/dev16.10 to release/dev16.10-vs-deps
…ase/dev16.10-vs-deps

Merge release/dev16.10 to release/dev16.10-vs-deps
…-4110-94f6-2fa5959b4a6d

Add localization from OneLocBuild (2021-05-07)
…ase/dev16.10-vs-deps

Merge release/dev16.10 to release/dev16.10-vs-deps
…ase/dev16.10-vs-deps

Merge release/dev16.10 to release/dev16.10-vs-deps
…ase/dev16.10-vs-deps

Merge release/dev16.10 to release/dev16.10-vs-deps
…ase/dev16.10-vs-deps

Merge release/dev16.10 to release/dev16.10-vs-deps
Merge release/dev16.9-vs-deps to release/dev16.10-vs-deps
…ase/dev16.10-vs-deps

Merge release/dev16.10 to release/dev16.10-vs-deps
@dotnet-bot dotnet-bot requested review from a team as code owners May 25, 2021 18:01
@dotnet-bot dotnet-bot requested a review from a team May 25, 2021 18:01
@dotnet-bot dotnet-bot added Area-Infrastructure auto-merge Merge Conflicts There are merge conflicts with the base branch. labels May 25, 2021
@dotnet-bot
Copy link
Collaborator Author

⚠ This PR has merge conflicts. @Cosifne

Copy link

@ghost ghost left a comment

Choose a reason for hiding this comment

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

Auto-approval

@Cosifne Cosifne removed the Merge Conflicts There are merge conflicts with the base branch. label May 25, 2021
@Cosifne
Copy link
Member

Cosifne commented May 25, 2021

I just saw the conflicts and then they are resolved @dibarbet Thanks!

@ghost ghost merged commit 28e77f5 into release/dev16.11 May 25, 2021
@ghost ghost deleted the merges/release/dev16.10-to-release/dev16.11 branch May 25, 2021 22:35
This pull request was closed.
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.