Skip to content

Merge release/dev17.4 to main#63372

Merged
dotnet-bot merged 71 commits intomainfrom
merges/release/dev17.4-to-main
Aug 16, 2022
Merged

Merge release/dev17.4 to main#63372
dotnet-bot merged 71 commits intomainfrom
merges/release/dev17.4-to-main

Conversation

@dotnet-bot
Copy link
Copy Markdown
Collaborator

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

dotnet-bot and others added 30 commits July 26, 2022 18:44
…to-main-vs-deps

Merge release/dev17.4-vs-deps to main-vs-deps
…to-main-vs-deps

Merge release/dev17.4-vs-deps to main-vs-deps
…to-main-vs-deps

Merge release/dev17.4-vs-deps to main-vs-deps
…to-main-vs-deps

Merge release/dev17.4-vs-deps to main-vs-deps
…to-main-vs-deps

Merge release/dev17.4-vs-deps to main-vs-deps
…to-main-vs-deps

Merge release/dev17.4-vs-deps to main-vs-deps
…to-main-vs-deps

Merge release/dev17.4-vs-deps to main-vs-deps
…to-main-vs-deps

Merge release/dev17.4-vs-deps to main-vs-deps
dotnet-bot and others added 10 commits August 10, 2022 21:13
Backport some integration test skips to 17.3
Revert "Merge pull request #61568 from CyrusNajmabadi/localFuncindexing"
…elease/dev17.3-to-release/dev17.4

* upstream/release/dev17.3:
  Revert "Merge pull request #61568 from CyrusNajmabadi/localFuncindexing"
  Backport some integration test skips to 17.3
  Mark shipped APIs (#63244)
…se/dev17.4

Merge release/dev17.3 to release/dev17.4
@dotnet-bot dotnet-bot requested review from a team as code owners August 13, 2022 00:02
@dotnet-bot dotnet-bot force-pushed the merges/release/dev17.4-to-main branch from 1d1e0cf to d69f080 Compare August 13, 2022 00:02
@dotnet-bot dotnet-bot added Area-Infrastructure auto-merge Merge Conflicts There are merge conflicts with the base branch. labels Aug 13, 2022
@dotnet-bot
Copy link
Copy Markdown
Collaborator Author

⚠ This PR has merge conflicts. @dibarbet

@dotnet-bot dotnet-bot enabled auto-merge August 13, 2022 00:02
Copy link
Copy Markdown

@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

@JoeRobich
Copy link
Copy Markdown
Member

@333fred Could you take a look at this merge conflict?

JoeRobich and others added 3 commits August 12, 2022 17:08
…elease/dev17.4-to-main

* upstream/release/dev17.4:
  Revert "Merge pull request #61568 from CyrusNajmabadi/localFuncindexing"
  Backport some integration test skips to 17.3
  Mark shipped APIs (#63244)
@dotnet-bot dotnet-bot merged commit 83a95a9 into main Aug 16, 2022
@ghost ghost added this to the Next milestone Aug 16, 2022
@dibarbet dibarbet modified the milestones: Next, 17.4 P2 Sep 1, 2022
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.

6 participants