This is a non-breaking new feature that addresses issue #129.
New input parameter:
- only_show_changed (default: false)
When true, shows only files that were changed by Prettier instead of
all processed files. Useful for large projects where output is
overwhelming.
Backward compatibility:
- When flag is NOT set or is false: behavior stays exactly as before
(shows "Files:" header and all prettier output)
- When flag is set to true: shows only "Changed files:" with git status
output for modified files
In projects with ~2,000 files, it's hard to see which were changed.
This optional flag makes it easy to identify modified files without
affecting existing users who rely on the current output format.
Closes#129
Refs prettier/prettier#2611
* allow `only_changed` and `dry` to work together
Before this change, if you tried to use `dry` and `only_changed together, it acted as if `only_changed` was ignored. There was no code specific to `only_changed` down the `dry` code path.
This commit’s solution is to run prettier on the entire code base (as was already being done) and then, before doing any comparisons, reset changes to files that were not modified in the last commit.
* add `only_changed_pr` option
This behaves similarly to only_changed, except instead of only considering files which were modified in the last commit, this option only considers files which were modified in any commit included in the current PR.
The entrypoint script checks for correctly named Prettier plugins on [lines 44–45](https://github.com/creyD/prettier_action/blob/master/entrypoint.sh#L44-L45), but the description in the config file and README are not consistent.
This updates those references to clarify how plugins should be specified.
