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
GrumPHP provides a way of fixing your code. However, we won't automatically commit the changes, so that you have the chance to review what has been fixed!
I actually experience that I always like all the automatic fixes. So if only automatic fixes were done, I'm just used to immediately committing again.
This is a compliment: I just trust Grumphp and the fixer. :)
So I wonder: Could I speed up my workflow by having an new opt-in configuration to continue with the commit if only automatic fixes have been applied?
The text was updated successfully, but these errors were encountered:
I've always been very sceptical for having this feature in Grumphp because I don't want to receive bug reports blaming us that our tool committed unwanted code to their codebase.
However, I do agree that having to recommit e.g. cs-fixer changes is a bit tedious.
For me, there are 2 ways to go here:
Our extension system is quite good : it should be possible to do it through an extension.
Thanks for the reply and the hints. Does sound like a little bit more work than I initially would've guessed, but I want to give it a try as soon as I find spare time. :)
2.5.0
We're using:
The documentation (https://github.com/phpro/grumphp/blob/v2.x/doc/parameters.md ) says:
I actually experience that I always like all the automatic fixes. So if only automatic fixes were done, I'm just used to immediately committing again.
This is a compliment: I just trust Grumphp and the fixer. :)
So I wonder: Could I speed up my workflow by having an new opt-in configuration to continue with the commit if only automatic fixes have been applied?
The text was updated successfully, but these errors were encountered: