This repository was archived by the owner on Dec 18, 2018. It is now read-only.
Reenable api check #2572
Merged
Reenable api check #2572
Conversation
This file contains hidden or 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
halter73
approved these changes
May 14, 2018
JunTaoLuo
force-pushed
the
johluo/api-check
branch
from
9c26df5 to
04f2101
Compare
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Addresses #2350. We have updated the runtimes of the buildtools which unblocked this issue. However won't we be broken again when something changes in the runtime future? Do we want to keep doing this or wait for the overhaul of the API checks at aspnet/BuildTools#594?
Tested locally.