Repository navigation
chore: drop the committed .idea leftover - #23
Merged
Merged
Conversation
A single 180-byte JetBrains vcs.xml whose entire content records that the project directory is a Git repo. It arrived in cab3e22 (2016) alongside an unrelated feature change. .gitignore has listed /.idea all along, but an ignore rule has no effect on a file that is already tracked, so it stayed. It never reached users either way: spec.files is a whitelist of lib/app/vendor/config/exe/bin plus README and LICENSE.
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.
Removes
.idea/vcs.xml, the only file under.idea/.Its entire content is:
So: a JetBrains project file recording that this directory is a Git repo. No paths from anyones machine, no names, no credentials — nothing sensitive, just noise.
It arrived in
cab3e22d(2016-04-27, "Ability to add custom ranges"), picked up alongside an unrelated feature change..gitignorehas listed/.ideathe whole time. That rule never had a chance: gitignore does not apply to files git is already tracking, so the entry could not evict what was committed before it.It never reached users regardless —
spec.filesis a whitelist (lib app vendor config exe bin README.md LICENSE.txt), so.ideawas never in the packaged gem.Checked the other 12 repos in the org: none of them carries a committed
.idea, so this is a one-off rather than a pattern worth a sweep.