-
Notifications
You must be signed in to change notification settings - Fork 601
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
Make references to NewRelic consistent #1795
Make references to NewRelic consistent #1795
Conversation
I fixed the failing tests, some renaming was needed |
Hi @fchatterji 👋 Thanks for submitting this PR and congrats on your first open source contribution 🥳 Your PR looks great so far! There are a few more changes that we'd love to see if you're open to making those updates. I'm also happy to merge as-is. Based on the sequel-related file name change of
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for making the additional updates. This looks great @fchatterji! I'll go ahead and merge your PR.
Hey @fchatterji! We needed to make an update to our CI, which is why your |
@hannahramadan yes that's what i thought, great. By the way, I noticed that you still have some newrelic_instrumentation in lib/new_relic/agent/instrumentation/active_record.rb. If you want I could change those too. |
Thanks for checking @fchatterji! All those instances of the string |
Before contributing, please read our contributing guidelines and code of conduct.
Overview
Pull request to make references to newrelic more consistent in the codebase, except in proto files and their dependencies
github issue: #1656
Submitter Checklist:
Testing
The agent includes a suite of unit and functional tests which should be used to
verify your changes don't break existing functionality. These tests will run with
GitHub Actions when a pull request is made. More details on running the tests locally can be found
here for our unit tests,
and here for our functional tests.
For most contributions it is strongly recommended to add additional tests which
exercise your changes.
Reviewer Checklist