-
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 master into features/recursive-patterns #32110
Merged
gafter
merged 28 commits into
dotnet:features/recursive-patterns
from
gafter:rpatterns-mergeQ
Jan 3, 2019
Merged
Merge master into features/recursive-patterns #32110
gafter
merged 28 commits into
dotnet:features/recursive-patterns
from
gafter:rpatterns-mergeQ
Jan 3, 2019
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
Since dotnet#30868, `ContentTypeNames` has moved to this assembly. Type forwarding doesn't seem to work for IVT.
Azure Pipelines now supports us putting the branches which trigger PR and CI validation into the YAML files. This change puts the current contents of our build definition into the YAML files and updates our creating feature branches document. Note: i have not yet changed our build definition to read this information. Want to commit this, give it a day to flow to the branches then I will flip our definition over.
Co-Authored-By: jaredpar <[email protected]>
It was out of date in a few places as projects have been moved/renamed/created.
Move CI / PR triggers to YAML files
Update build, debug, test doc
Cache the return values for GetIdForErrorCode
Random code comment typo fixes
Fixed adding attribute list with target specifier
…ember Rename an enum member to be clearer, and add docs as well.
EditorFeatures.Text IVTs for MonoDevelop
Consistently parse .editorconfig option values containing spaces
…otnet#31782) * Fix additional newlines being added when adding all missing imports * Use syntax formatter to remove extra newlines when adding missing imports * Apply suggestions from code review * Added assert to ensure we retain the final newline * Updated the assert to include cases where a newline pre-existed
…#32005) For each reference that doesn't have an .XML doc file we allocate and cache a FileBasedXmlDocumentationProvider that throws a first-chance exception upon first use. Add and use a singleton NullXmlDocumentationProvider instead when the requested .XML doc file doesn't exist.
…et/roslyn into rpatterns-mergeQ
@jaredpar Would you like to do the honors of merging this? |
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.
No description provided.