chore(dev): Enforce frontend filename casing in pre-commit#120081
Closed
sentry-junior[bot] wants to merge 1 commit into
Closed
chore(dev): Enforce frontend filename casing in pre-commit#120081sentry-junior[bot] wants to merge 1 commit into
sentry-junior[bot] wants to merge 1 commit into
Conversation
Case-only renames (Foo.tsx -> foo.tsx) break macOS case-insensitive checkouts when casing drifts across branches. check-case-conflict only catches two distinct colliding paths, not a single-file rename. Co-Authored-By: Markus Unterwaditzer <markus@sentry.io>
github-actions
Bot
added
the
Scope: Backend
sentry-junior
Bot
changed the title
sentry-junior
Bot
force-pushed
the
chore/prevent-case-only-rename
branch
from
July 20, 2026 17:46
76a18f8 to
60610d5
Compare
Member
|
replaced by #120103 |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Block case-only renames and require new frontend modules to be named correctly up front.
Case-only renames break macOS case-insensitive checkouts when casing drifts across branches.
check-case-conflictonly catches two distinct colliding paths, not a single-file rename. Filename/export mismatches (metricHeatmapApiOptionsvsmetricHeatMapApiOptions) are what create the need for those renames.Checks (
tools/check_frontend_filenames.py)Foo.tsx→foo.tsx)static//tests/js/:HTTPSnippet→httpSnippet)Existing mismatched files are left alone; only new adds / real renames are gated.