This repository was archived by the owner on Oct 13, 2025. It is now read-only.
Move tracing-events into ./scripting #311
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
evantypanski
approved these changes
May 6, 2025
Contributor
evantypanski
left a comment
evantypanski
left a comment
There was a problem hiding this comment.
I prefer this by a lot!
| usage | ||
| event-groups | ||
| optimization | ||
| tracing-events |
Contributor
There was a problem hiding this comment.
nit: I'd personally prefer this go above optimization since it's tangentially related to event-groups
awelzel
force-pushed
the
topic/awelzel/move-tracing-events-to-scripting
branch
from
9145fa8 to
02a26df
Compare
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
@evantypanski - what do you think about just doing that now?
I made Vern the author as I have no
beef inauthorship for the content :-)