Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
When an existing hook uses a lint-staged-only flag such as
--difffor CI/branch diffs, this migration reference now points to help but no longer says to keep standalone lint-staged for unsupported flags. I checkedpackages/rstack/src/staged.ts:parseArgsisstrict: trueand thers stagedhelp only lists--allow-empty,--concurrent,--cwd,--debug,--no-stash,--quiet,--relative, and--verbose, while lint-staged's own help includes additional flags like--diff [string]to override the defaultgit diff --stagedbehavior and--fail-on-changes; migrating those scripts tors stagedwill fail on the unknown option, so this section should explicitly say only the listed options can be carried over.Useful? React with 👍 / 👎.