Skip to content

Merge release/dev16.8-vs-deps to release/dev16.9-vs-deps#48778

Merged
7 commits merged intorelease/dev16.9-vs-depsfrom
merges/release/dev16.8-vs-deps-to-release/dev16.9-vs-deps
Oct 21, 2020
Merged

Merge release/dev16.8-vs-deps to release/dev16.9-vs-deps#48778
7 commits merged intorelease/dev16.9-vs-depsfrom
merges/release/dev16.8-vs-deps-to-release/dev16.9-vs-deps

Conversation

@dotnet-bot
Copy link
Collaborator

This is an automatically generated pull request from release/dev16.8-vs-deps into release/dev16.9-vs-deps.

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

@dotnet-bot dotnet-bot requested review from a team as code owners October 20, 2020 00:02
@dotnet-bot dotnet-bot requested a review from a team October 20, 2020 00:02
@dotnet-bot dotnet-bot added Area-Infrastructure auto-merge Merge Conflicts There are merge conflicts with the base branch. labels Oct 20, 2020
@ghost
Copy link

ghost commented Oct 20, 2020

Hello @dotnet-bot!

Because this pull request has the auto-merge label, I will be glad to assist with helping to merge this pull request once all check-in policies pass.

Do note that I've been instructed to only help merge pull requests of this repository that have been opened for at least 12 minutes. No worries though, I will be back when the time is right! 😉

p.s. you can customize the way I help with merging this pull request, such as holding this pull request until a specific person approves. Simply @mention me (@msftbot) and give me an instruction to get started! Learn more here.

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

…rges/release/dev16.8-vs-deps-to-release/dev16.9-vs-deps
@RikkiGibson
Copy link
Member

CI failures appear to be due to network issues in AzDo.

@ghost ghost merged commit 182c1e3 into release/dev16.9-vs-deps Oct 21, 2020
@ghost ghost deleted the merges/release/dev16.8-vs-deps-to-release/dev16.9-vs-deps branch October 21, 2020 00:18
This pull request was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Area-Infrastructure auto-merge Merge Conflicts There are merge conflicts with the base branch.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants