| commit | ae6cb08ae52d488a4cc6892f811c1c1acf8c3c12 | [log] [tgz] |
|---|---|---|
| author | Mike Frysinger <vapier@google.com> | Tue Aug 27 01:10:59 2019 -0400 |
| committer | Mike Frysinger <vapier@google.com> | Wed Aug 28 03:54:11 2019 +0000 |
| tree | c927415df288d9bf9076e758835db53cc633597d | |
| parent | 3fc157285cb61d6a4faa55dc4f011fb94d598c20 [diff] |
split out cli validation from execution A common pattern in our subcommands is to verify the arguments & options before executing things. For some subcommands, that check stage is quite long which makes the execution function even bigger. Lets split that logic out of the execute phase so it's easier to manage these. This is most noticeable in the sync subcommand whose Execute func is quite large, and the option checking makes up ~15% of it. The manifest command's Execute can be simplified significantly as the optparse configuration always sets output_file to a string. Change-Id: I7097847ff040e831345e63de6b467ee17609990e Reviewed-on: https://gerrit-review.googlesource.com/c/git-repo/+/234834 Reviewed-by: David Pursehouse <dpursehouse@collab.net> Tested-by: Mike Frysinger <vapier@google.com>
Repo is a tool built on top of Git. Repo helps manage many Git repositories, does the uploads to revision control systems, and automates parts of the development workflow. Repo is not meant to replace Git, only to make it easier to work with Git. The repo command is an executable Python script that you can put anywhere in your path.