Merged
Conversation
Somehow (apparently after #3494) we wound up with a bunch of duplicate folders in our repo, both the old title-case names and the new lower-case names. All of the remaining files in the title-case directories have their last change in #3343, well before #3494, so I don't believe we're losing any intermediate changes by deleting them. I'm not sure how this happened, but it seems to be an easy fix.
cloutiertyler
approved these changes
Nov 26, 2025
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
2 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 Changes
Somehow (apparently after #3494) we wound up with a bunch of duplicate folders in our repo, both the old title-case names and the new lower-case names. All of the remaining files in the title-case directories have their last change in #3343, well before #3494, so I don't believe we're losing any intermediate changes by deleting them. I'm not sure how this happened, but it seems to be an easy fix.
API and ABI breaking changes
N/a
Expected complexity level and risk
2 - some small possibility that I accidentally deleted an intentional change that got borked by a merge conflict or something. I don't think I did, tho, based on the age of the git blame on the files deleted here.
Testing
None