Bazel Deprecation #207
Merged
Bazel Deprecation #207
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
- Adds a deprecation warning to the exported rules and points to the migration docs
|
Fixes #171. |
jonny-improbable
approved these changes
Oct 22, 2019
|
Lovely stuff, thanks for your stewardship @Dig-Doug. |
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.
Follow up to this discussion.
This change does the following:
READMEREADMEto point to the new implementation.After this PR, the only remaining pieces of bazel related code are the
WORKSPACE, theBUILD, and thedefs.bzlfiles. They can be cleaned up sometime in the future.