You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Sometimes, when the gem is dealing with a situation such as the one addressed in the fix for #20, the gem states that a file is being modified but the file ends up being unchanged.
This is specifically an issue when the prior two-newline issue would have previously occurred. Now, the newline issue is addressed, but the gem still claims the file is modified.
➜ git:(development) ✗ rake cleanup:jumpstart
Running via Spring preloader in process 7838
Starting cleanup:jumpstart
./spec/models/a_model_spec.rb modified.
./spec/lib/includers/a_lib_spec.rb modified.
Finishing cleanup:jumpstart
➜ git:(development) ✗ git status spec
On branch development
Your branch is up to date with 'origin/development'.
Changes not staged for commit:
(use "git add <file>..." to update what will be committed)
(use "git checkout -- <file>..." to discard changes in working directory)
modified: spec/models/a_model_spec.rb
The text was updated successfully, but these errors were encountered:
Sometimes, when the gem is dealing with a situation such as the one addressed in the fix for #20, the gem states that a file is being modified but the file ends up being unchanged.
This is specifically an issue when the prior two-newline issue would have previously occurred. Now, the newline issue is addressed, but the gem still claims the file is modified.
The text was updated successfully, but these errors were encountered: