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

Strange behavior of isDirty #43

Open
Alex66955 opened this issue Jul 17, 2018 · 1 comment
Open

Strange behavior of isDirty #43

Alex66955 opened this issue Jul 17, 2018 · 1 comment

Comments

@Alex66955
Copy link

I have some trouble with the isDirty function.

In one of my git projects I got always true returned. But the git status returns no changes.
I executed the git commands behind isDirty manually and got the same results:
git diff-index c7f53b57c5b8ea9a2e3c837a09bbef6dc668b561 . :100644 100644 e0de748c18601e6860e667b97c12b9de3212dfb2 0000000000000000000000000000000000000000 M recovery/downloadmanager/public/resources/version.json :100644 100644 a4bc9e8488bc52856ad6836643d4f06010ded752 0000000000000000000000000000000000000000 M recovery/downloadmanager/src/resources/password.json :100644 100644 e0de748c18601e6860e667b97c12b9de3212dfb2 0000000000000000000000000000000000000000 M recovery/downloadmanager/src/resources/version.json

but my git status show always:
developer@ubuntu:/data/ngc/recovery/downloadmanager$ git status On branch features/secure-image-file Your branch is up-to-date with 'origin/features/secure-image-file'. nothing to commit, working directory clean

Is there any idea to fix my issue?

@kurttheviking
Copy link
Owner

It looks like the previous isDirty implementation didn't quite reflect what you may have intended; #46 may have fixed things

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

No branches or pull requests

2 participants