ci: Add NR1 Lib Deprecation Check Workflow #14
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.
PR Explanation
Hello from the Developer Ecosystem team at New Relic! This PR contains a GitHub actions workflow which runs Repolinter, an automated tool to help us find and fix inconsistencies in our public repositories. This PR registers a GitHub Actions workflow (
nr1_lib_deprecations.yml
) running repolinter-action. The goal of this workflow is to validate that your New Relic One application is making use of the most currentnr1
JS libraries by reporting any deprecation warnings or errors.Repolinter Action does
with.config-url
: this ruleset will be maintained by the Open Source and Developer Advocacy team and will not change frequently.repolinter
label. This issue will contain detailed information on which policies generated errors and what changes are suggested.This workflow is designed to cause the least amount of friction as possible:
What you should do
repolinter
label). If an issue is opened, look it over and make sure all the problems seem correct. Shoot us a ping in #help-opensource if anything looks suspicious.If you have feedback, please let us know in #help-opensource. Thanks!