Merge main to features/list-patterns #55321
Merged
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
dotnet-bot
added
Area-Infrastructure
auto-merge
Merge Conflicts
…oBounds is needed
…for other languages
…#55713) Co-authored-by: Sam Harwell <Sam.Harwell@microsoft.com>
Have inheritance-margin hold onto data that does *not* point back at Solution instances.
…eBackgroundFix Change the head of inheritance margin background to InActiveTextBox
[main] Update dependencies from dotnet/source-build
…wMargin Add an option to let user could change the position of Inheritance Margin
* Add generator drive cache to VBCSCompiler: - Create a new cache type - Make the compiler optionally take it - Pass in the cache when running on the server - Check the cache (if there is one) for a generator driver before creating a new one - Add feature flag to disable cache - Disable the cache when there isn't an output file name Co-authored-by: Charles Stoner <chucks@microsoft.com>
Remove RemoveUnusedReferences command hotkey
Add Import Directives to the VS options search text
Fix typing in rename preview changes
Remove experimental suffix for inheritance margin
…-to-release/dev17.0 Merge release/dev16.11-vs-deps to release/dev17.0
Merge main into release/dev17.0
Update version for preview 5
Merge release/dev17.0 to main
Merge release/dev17.0 to main
* Track duplicate hintNames as they are added
… 20210831.1 (#56060) [main] Update dependencies from dotnet/source-build
Update OneLoc build branch
Merge release/dev17.0 to main
…ges/main-to-features/list-patterns
JoeRobich
removed
the
Merge Conflicts
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/list-patterns.
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/list-patterns git reset --hard upstream/features/list-patterns git merge upstream/main # Fix merge conflicts git commit git push upstream merges/main-to-features/list-patterns --force