-
Notifications
You must be signed in to change notification settings - Fork 177
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unexpected ignore coloring of nested file listed as a top level ignore only #112
Comments
Sure, just let me know how :-) |
Great. It's available here: https://github.com/hsz/idea-gitignore/releases/tag/v1.1.2-RC |
Good news / bad news. With that RC #105 appears fixed, but the gradle.properties in a subdir is still being ignored. Just to clarify this is not a nested Git root, just a plain ole boring subdir :-) In that screenshot For reference the parent repo with the gradle.properties is https://github.com/MovingBlocks/Terasology (the copy at the root was manually duplicated from the template, no magic involved) For completeness here's the content of the template .gitignore (which shouldn't be in play at all since it is not in a Git root, and it doesn't have any related entries)
|
With following command:
you can check what files are mathed by the As I can see, the Currently, VCS files index is not respected by the plugin. It's using only the rules from ignore files. |
Ooohh. So you mean that file would normally have been ignored, but since it already exists in the repo what git returns on the command line clashes with how it ideally should work? Yeah it is entirely possible if not probable that entry was added to the ignore later. My apologies for the inconvenience in that case :-) |
Fix has ben released just right now with |
Just noticed this - I have "gradle.properties" in my .gitignore, which is a root level file and not controlled by Git in this case. However I also have a template version of the file in a nested directory that is in Git. The plugin marks the nested version as ignored, yet Git reports it as changed (which is what I expect - in this case I have a pending change in it). I would think the nested gradle.properties at this point should be highlighted in blue, which it becomes if I take out the entry in the .gitignore.
Example:
Incidentally the .gitignore inside the templates directory naturally is itself a template and doesn't have a gradle.properties entry in it.
I'm not entirely sure how to get gradle.properties at any location gitignored just to see what happens, but then I don't need that either so that's ok :-)
The text was updated successfully, but these errors were encountered: