-
Notifications
You must be signed in to change notification settings - Fork 245
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
pronto doesn't analyse staged changes #111
Comments
@konradstrack I've created an issue on rugged repo. |
Changing this from Will make it part of the next release, because an integration with overcommit would be great. |
I've also come across this issue. |
|
@mmozuras any update on how to use this with staged changes? |
@konradstrack @elliotthilaire @KirillSuhodolov @MvanDiemen I've renamed the |
@KirillSuhodolov @glennr you can find the PR on Overcommit for a pre-commit hook here: sds/overcommit#488 😄 |
I've been trying to execute pronto in a pre-commit hook, and I ended up with the following issue.
Suppose I have a file with inorrect indentation: in this case it's
Gemfile
. I stage it withgit add Gemfile
and executepronto run --index
. No issues are reported.Now, if I do
git reset Gemfile
,pronto run --index
will report the issues correctly, e.g.:I tested a bit more, and staged changes are not being analysed with all of the following:
pronto run
,pronto run --index
,pronto run --commit=$(git log --pretty=format:%H | head -1)
,pronto run --commit=HEAD
.Is there something trivial I have missed, or is this behaviour expected?
I used Ruby 2.1.5. More info:
The text was updated successfully, but these errors were encountered: