superproject: Only trigger enrollment logic when manifest have it.

The current code would check for enrollment status when the user did not
explicitly specify --[no-]use-superproject and do not have a remembered
value in their repo client. However, because superproject only makes
sense for manifests that have one specified, we should skip the
enrollment logic in that case.

Address this by checking manifest.superproject prior to proceeding. This
would avoid showing the greeting message of superproject enrollment
which can be confusing for developers.

Tested:
  For manifest without superproject:
   - repo sync --use-superproject will still show message for
     superproject;
   - repo sync will not show message regardless of enrollment state
  For manifest with superproject:
   - repo sync will show message and perform enrollment if not
     previously enrolled

Bug: https://crbug.com/gerrit/15039
Change-Id: Ic2be9f9d037f0e7cf3446da474a5a0d0e4bd88da
Reviewed-on: https://gerrit-review.googlesource.com/c/git-repo/+/319255
Tested-by: Xin Li <delphij@google.com>
Reviewed-by: Raman Tenneti <rtenneti@google.com>
Reviewed-by: Mike Frysinger <vapier@google.com>
1 file changed
tree: 9b84d88dfba4c2138bca0daef68e7aa025b00718
  1. .github/
  2. docs/
  3. hooks/
  4. man/
  5. release/
  6. subcmds/
  7. tests/
  8. .flake8
  9. .gitattributes
  10. .gitignore
  11. .mailmap
  12. .project
  13. .pydevproject
  14. color.py
  15. command.py
  16. completion.bash
  17. editor.py
  18. error.py
  19. event_log.py
  20. fetch.py
  21. git_command.py
  22. git_config.py
  23. git_refs.py
  24. git_ssh
  25. git_superproject.py
  26. git_trace2_event_log.py
  27. gitc_utils.py
  28. hooks.py
  29. LICENSE
  30. main.py
  31. MANIFEST.in
  32. manifest_xml.py
  33. pager.py
  34. platform_utils.py
  35. platform_utils_win32.py
  36. progress.py
  37. project.py
  38. README.md
  39. repo
  40. repo_trace.py
  41. requirements.json
  42. run_tests
  43. setup.py
  44. ssh.py
  45. SUBMITTING_PATCHES.md
  46. tox.ini
  47. wrapper.py
README.md

repo

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.

Contact

Please use the repo-discuss mailing list or issue tracker for questions.

You can file a new bug report under the “repo” component.

Please do not e-mail individual developers for support. They do not have the bandwidth for it, and often times questions have already been asked on repo-discuss or bugs posted to the issue tracker. So please search those sites first.

Install

Many distros include repo, so you might be able to install from there.

# Debian/Ubuntu.
$ sudo apt-get install repo

# Gentoo.
$ sudo emerge dev-vcs/repo

You can install it manually as well as it's a single script.

$ mkdir -p ~/.bin
$ PATH="${HOME}/.bin:${PATH}"
$ curl https://storage.googleapis.com/git-repo-downloads/repo > ~/.bin/repo
$ chmod a+rx ~/.bin/repo