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
Is your feature request related to a problem? Please describe.
When introducing a "dirty" project to treefmt, it can create a lot of code churn as files that previously weren't formatted are now getting changed. You often end up with a fat commit that formats the whole repo and breaks git blame.
Describe the solution you'd like
When the file backend is git, only format the untrack and changed files by default.
Add a --all-files flag to override that default.
Describe alternatives you've considered
Additional context
The text was updated successfully, but these errors were encountered:
If the modified time has not changed when compared with the git index we do not emit the file for processing.
This allows users to introduce treefmt to a repository without suffering an initial large formatting commit.
Instead, files can be formatted incrementally as they are changed.
Closes#311
Signed-off-by: Brian McGee <brian@bmcgee.ie>
If the modified time has not changed when compared with the git index we do not emit the file for processing.
This allows users to introduce treefmt to a repository without suffering an initial large formatting commit.
Instead, files can be formatted incrementally as they are changed.
Closes#311
Signed-off-by: Brian McGee <brian@bmcgee.ie>
Is your feature request related to a problem? Please describe.
When introducing a "dirty" project to treefmt, it can create a lot of code churn as files that previously weren't formatted are now getting changed. You often end up with a fat commit that formats the whole repo and breaks
git blame
.Describe the solution you'd like
When the file backend is git, only format the untrack and changed files by default.
Add a
--all-files
flag to override that default.Describe alternatives you've considered
Additional context
The text was updated successfully, but these errors were encountered: