> Also, it makes a more sense to "add" the file before indenting it, to > allow checking the output and remove unrelated changes. So that doesn't > seem to me like a restriction of any significance.
For my workflow it would be the same, but afaik there's two ways that people commonly use git (mine is 1): 1. Adding changes/files to the staging area using and then committing those changes: git add (-p)/emacs magit/some other editor integration 2. Just add everything that's changed and commit all of it: git add -A + git commit/git commit -a For workflow 1, a --staged/--cached flag would be enough IMHO. But that's not at all helpful for workflow 2. That's why I proposed --uncommitted too, to make indenting easier for workflow 2. > But I would never want to indent an untracked file unless I specified > it. Would the --uncommitted flag I proposed be enough of an explicit way of specifying that you want to indent untracked files?