Convert filename to follow snake_case convention #119899
Closed
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
kpatticha
force-pushed
the
convert-comp-to-snake_case
branch
from
9cb3796 to
19bee2e
Compare
kpatticha
force-pushed
the
convert-comp-to-snake_case
branch
from
19bee2e to
1a4cea9
Compare
2 tasks
kpatticha
force-pushed
the
convert-comp-to-snake_case
branch
from
1a4cea9 to
c695bfd
Compare
kpatticha
force-pushed
the
convert-comp-to-snake_case
branch
from
c695bfd to
55651fc
Compare
💔 Build FailedFailed CI Steps
Test Failures
Metrics [docs]Unknown metric groupsESLint disabled in files
Total ESLint disabled count
History
To update your PR or re-run it, just comment with: |
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.
Summary
WIP, convert public filename to follow snake_case convention