feat: repolinter rules for NR1 lib deprecations #24
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
|
Thanks to @prototypicalpro for the assist this weekend! |
jbeveland27
reviewed
Jan 11, 2021
|
Also worth mentioning, this approach is 🔥 |
added 2 commits
January 11, 2021 12:50
jpvajda
suggested changes
Jan 11, 2021
Co-authored-by: John P Vajda <jvajda@newrelic.com>
Co-authored-by: John P Vajda <jvajda@newrelic.com>
Co-authored-by: Noah Koontz <nkoontz@newrelic.com> Co-authored-by: John P Vajda <jvajda@newrelic.com>
|
Is this ready to merge in? 🙏 |
|
🥳 |
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.
Addressing deprecation warnings/errors via a repolinter rule. Once this is in the main, I'll PR all repos that have nr1 artifacts.