When cloning a repo from the repository list, everything would just be populated in no particular order. This PR puts all forks in a expandable list underneath the parent repository name.
Side Note
After merging changes from master into this branch, the method displayBranch in repo.ts didn't seem to be used anymore, rather the method displayRepo in authenticate.ts was being used to populate the repo list. I tried deleting the displayRepo method entirely and the whole thing seemed to still work. I've left the method in now for arguments sake, but later we might want to get rid of it if its actually useless.
Testing:
Needs to be manually tested
Steps for manual testing:
Open and log into Visual Git
Click repository from up top (ie. go and clone one of your repos)
Observe that forks are listed under the main repository's header and by clicking said header, the list expands to all forks available
Clone a repo to make sure cloning is still all good
Checklist:
[x] Latest master merged/rebased into your feature branch
[ ] Tests covering all changes (see above)
[x] Meets the projects coding conventions
[x] No out of scope changes
[x] No failure when running the linter (npm run lint)
Ravid12
commented
5 years ago
Related Issue/Keyword:
Closes #37
Description:
When cloning a repo from the repository list, everything would just be populated in no particular order. This PR puts all forks in a expandable list underneath the parent repository name.
Side Note
After merging changes from master into this branch, the method displayBranch in repo.ts didn't seem to be used anymore, rather the method displayRepo in authenticate.ts was being used to populate the repo list. I tried deleting the displayRepo method entirely and the whole thing seemed to still work. I've left the method in now for arguments sake, but later we might want to get rid of it if its actually useless.
Testing:
Needs to be manually tested
Steps for manual testing:
Checklist:
npm run lint)