Add stgit.new.verbose config option
commitc17cf5e6c66c37bbb438e95c3af0e5dd132daae6
authorPeter Grayson <pete@jpgrayson.net>
Sun, 26 Sep 2021 13:01:00 +0000 (26 09:01 -0400)
committerPeter Grayson <pete@jpgrayson.net>
Sun, 26 Sep 2021 13:21:24 +0000 (26 09:21 -0400)
tree2c7b7df1263d2840273788a39ed5144792c418b7
parent52156927e41a1f5ae802cdd0975a80023d51d8eb
Add stgit.new.verbose config option

Instead of piggybacking on Git's commit.new config option, StGit now has
its own config option for turning-on `stg new --verbose`.

Two considerations for this change:

- `stg new` does not refresh, thus it leaves changes in the worktree.
  This is a significant semantic difference with `git commit` that makes
  reuse of `commit.verbose` an awkward fit.

- The performance implications in large monorepos with `stg new
  --verbose` versus `git commit --verbose` are quite different. See
  #145. The gist is that the diff operation needed for `stg new
  --verbose` can be much more expensive than `git commit --verbose`.

Signed-off-by: Peter Grayson <pete@jpgrayson.net>
CHANGELOG.md
stgit/commands/new.py
t/t1003-new.sh