-
Notifications
You must be signed in to change notification settings - Fork 4.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merge main to features/caller-argument-expression #52405
Merged
203 commits merged into
features/caller-argument-expression
from
merges/main-to-features/caller-argument-expression
Apr 4, 2021
Merged
Merge main to features/caller-argument-expression #52405
203 commits merged into
features/caller-argument-expression
from
merges/main-to-features/caller-argument-expression
Apr 4, 2021
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Closes AB#761238
The correct value for this option is sourced from ITaskList. Including a default value hides cases where options fail to load.
We're not entirely sure why this was added; it might have been due to lack of Assert.ThrowsAsync in whichever version of xUnit we were using, or something else. In any case, it's unnecessary today and was also broken: it would silently succeed if the passed function didn't throw any exceptions at all.
Co-authored-by: Sam Harwell <sam@tunnelvisionlabs.com>
…onExtensions.cs Co-authored-by: Joey Robichaud <joseph.robichaud@microsoft.com>
Remove unnecessary test delays
Fix Quick Info integration tests
…okens Enforce passing CancellationTokens were present
Merge release/dev16.10 to main
Handle typeof expression in complete statement
Fix namespaces
Avoid OOP syncing when doing a nav-to search during the initial load of a solution.
…e-fix Import System namespace when adding null check
Fix tuple naming
ghost
approved these changes
Apr 4, 2021
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Auto-approval
This pull request was closed.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is an automatically generated pull request from main into features/caller-argument-expression.
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/main-to-features/caller-argument-expression git reset --hard upstream/features/caller-argument-expression git merge upstream/main # Fix merge conflicts git commit git push upstream merges/main-to-features/caller-argument-expression --force