Using a cloud-based VCS

From Authorizing Access to Your Source Code, you will have already set up the OAuth credentials to allow logins to your preferred VCS. Assuming that you have done that, select your VCS from the pull-down menu. For our examples, we will be using GitHub.

The very first time a user attempts to reach GitHub following the OAuth configuration, the Navigator will pop up a window requesting you to enter the Client ID and Secret keys from the OAuth configuration.

As explained in Authorizing Access to Your source code, hopefully you copied the Client ID and Secret somewhere so that you can enter them here. Once done, users may login into their GitHub accounts without needing to repeat this process.

If there is some reason to change the OAuth Client ID and Secret, you can get back to this window using the Settings button on the main menu.

If you are already logged into GitHub from earlier activity on your browser, then your repository will become available right away. If your login session is no longer active, you may be asked to renew it with this prompt.

After selecting Yes, you will need to re-select the GitHub repository.

Once logged in, you will now see all of your available GitHub projects.

Each project is presented with a “+” sign so that you can open it up to view its branches. Before you can browse the project branches, however, you need to "clone" a copy of the project from GitHub. The Clone button is to the right of the project name box.

For our example, we will use a project called Baritone, which we show below as cloned and ready for analysis. Note that, once cloned, the Clone button is replaced by Remove. This provides you with a way of removing a project if you desire. When you remove a project, however, note that ALL RESULTS WILL BE REMOVED. That is, any analyses that you have performed and not applied to your project will be lost. Clicking on the “+” will enumerate all of the available branches: