Skip to content
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

false positive: Ignored files found that are tracked #361

Closed
KingMario opened this issue May 14, 2017 · 5 comments
Closed

false positive: Ignored files found that are tracked #361

KingMario opened this issue May 14, 2017 · 5 comments

Comments

@KingMario
Copy link

KingMario commented May 14, 2017

I have the following entries in .gitignore

frontend/node_modules/
!frontend/node_modules/clarity-angular/
!frontend/node_modules/clarity-ui/

But the plugin reports the following alarm

Ignored files found that are tracked: .ignore plugin found some files that are tracked with Git which are also listed in .gitignore file.

Click the Show Detail link, and I find that it's about the files under frontend/node_modules/clarity_angular and frontend/node_modules/clarity-ui/.

Besides, there are many entry is never used alarms in the file which meaning is unsure.

image

Did I understand something wrong?

@osahner
Copy link

osahner commented May 19, 2017

I second that. Mostly gone after reopen.

@Hronom
Copy link

Hronom commented May 23, 2017

I'm using latest release of this plugin and also have problem with excluded folders:

*.jar
!/libs/**/*

The plugin wants untrack all .jar files inside /libs directory.

@mko-x
Copy link

mko-x commented May 24, 2017

Same Problem here with PHPStorm.

Project source code files are randomly marked as ignored with warning in IDE if opened. This happened several times to definitely not excluded or ignored files now.

image

@YOzaz
Copy link

YOzaz commented May 24, 2017

Same here.

@hsz hsz added this to the v2.0 milestone May 28, 2017
@hsz hsz added the bug label May 28, 2017
@hsz
Copy link
Member

hsz commented Jun 5, 2017

@KingMario @osahner @Hronom @mko-x @YOzaz @iandbanks

Thanks for this report!

This issue has been resolved - commit is attached to #350.
Fix will be released soon with v2.0.0 version.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants