chore(tracer): rename package folder to tracer #854
Merged
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
dreamorosi
added
tracer
13 tasks
flochaz
approved these changes
May 12, 2022
dreamorosi
added a commit
that referenced
this pull request
Aug 2, 2022
* chore: renamed tracer folder * chore: update package name * chore: renamed util in e2e workflow
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Description of your changes
As described in #829 the
Tracerutility was referred to as tracer across the whole project, except for the folder name that waspackages/tracing.This PR renames the folder & updates relevant files.
Note: while the number of modified files is high, the files with a diff are only three; all others are renames derived from the folder name change.
Fixes #829
How to verify this change
See result of GitHub actions under this PR which should continue passing.
Related issues, RFCs
#829
#26
PR status
Is this ready for review?: YES
Is it a breaking change?: NO
Checklist
Breaking change checklist
N/A
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.