-
Notifications
You must be signed in to change notification settings - Fork 144
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
feat: Add a --with-exit-status flag #270
feat: Add a --with-exit-status flag #270
Conversation
app/Commands/DefaultCommand.php
Outdated
@@ -43,6 +43,7 @@ protected function configure() | |||
new InputOption('dirty', '', InputOption::VALUE_NONE, 'Only fix files that have uncommitted changes'), | |||
new InputOption('format', '', InputOption::VALUE_REQUIRED, 'The output format that should be used'), | |||
new InputOption('cache-file', '', InputArgument::OPTIONAL, 'The path to the cache file'), | |||
new InputOption('with-exit-status', '', InputOption::VALUE_NONE, 'Only fix files that have uncommitted changes'), |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think the description here might be incorrect (copied and pasted from a few lines above?)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oops, didn't even see that. I'll fix that up and write any relevant tests as there seems to be interest in this feature.
Hey @dshafik, thanks for the PR! I'll mark this as draft for now as you're still working on this. Feel free to mark as ready when you need another review. |
@driesvints Fixed up the one issue and added tests, this is ready for review now 🙏🏻 |
Thanks! |
This adds a small feature,
--with-exit-status
that will exit with either 1 or 0 if there are changed files or not. Essentially this is the same as running with the--test
flag except that it also changes the files.This is helpful for tools such as Captain Hook (or really any pre-commit hook) which rely on the exit code to know if there were changes, so that it will fail and allow amending the commit manually.
it should be noted that while it seems the prevailing consensus is that you should just run
pint
and then automatically add the changed files to the commit, however if you have additional working changes (e.g. you only staged part of the file, or made changes after staging it) then those changes would now be inadvertently included in the commit.Happy to add tests if this is a feature you feel would be worth contributing.
Docs PR: laravel/docs#9606