-
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
[1.x] Adds --dirty
option
#130
Conversation
Introduce `--dirty` for Git projects
@nunomaduro, thanks for the guidance. I'll get this patched up in the next live stream unless baby Emma comes early. 👨🍼 |
Just finished up my live stream. I got items 1 and 2 working. A quick caveat though, the In reviewing that and item 3, it appears |
Looks cool!, Currently using lint-staged for this "lint-staged":{
"**/*.{php}": [
"./vendor/bin/pint"
],
"resources/js/**/*.{js,vue}": [
"prettier --write",
"eslint --fix"
]
} |
Filter deleted and renamed files
This pull request, developed in collaboration with @jasonmccreary, adds the --dirty option to Pint. When this option is used, Pint will only apply styling changes to added or edited files in a Git repository.
This means that when you use this option in a pull request for your project, Pint will style only the files you have added or edited, and not style any files that were not modified by your pull request.