Skip to content

Conversation

@dotnet-bot
Copy link
Contributor

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

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

majocha and others added 5 commits March 14, 2023 10:56
)

* Searching functions for Array.Parallel added

* with [<Experimental("Experimental library feature, requires '--langversion:preview'")>] annotation to give us space to change/remove this API in the future if needed
* Add GraphNode.FromResult

* fantomas
* Fix missing reference

* undo whitespace change
@vzarytovskii vzarytovskii merged commit 9a48514 into release/dev17.6 Mar 14, 2023
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.

8 participants