If your code affects repository cloning, or the repo tool, please manually verify these scenarios. This is required for all PRs that affect repo cloning directly or indirectly. Indirectly can be changes in DeveloperId code in an extension or an SDK change.
Please make sure to verify all these scenarios.
- Multiple repos can be selected and added in bulk and the selected repos show up in the repo config screen.
- User can clone a forked repo.
- If provided a URL to an existing repo, and the user has access to the repo, it shows up on the repo config page.
- User can clone a public repo without being signed in.
- All repos shown on this page have the correct information, including icon, repo name, provider name, and clone location.
- All repos selected in the repo tool are cloned to their respective locations.
- Any failures are logged and shown to the user.
- If the user is logged in to the repository provider, clicking on the "Account" tab brings the user to the list of repos they have access to.
- The account tab displays a list of all enabled providers the user can choose. The names displayed are the long form. Example "Dev Home GitHub Extension (Dev)" and not "GitHub".
- User can edit a repository’s full path on their disk drive