Using a cloud-based VCS

From Authorizing Access to Your Source Code, you will have already set up the OAuth credentials or your Personal Access Token (PAT) to allow access 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 cloud as the chosen VCS.

The very first time a user attempts to reach GitHub following the OAuth/PAT configuration, the Navigator will pop up a window asking you to choose whether or not you plan to use OAuth credentials or your PAT:

In this first case, we show how to configure the OAuth credentials, so we click on Proceed with OAuth. This opens a dialog box 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. Click the Submit button to accept the changes. Once done, users may login into their GitHub accounts without needing to repeat this process.

If you have chosen to authenticate using your private PAT, the above process is a little different. In this case, select Proceed with PAT. This brings up the popup asking for the PAT information.

As described in Authenticating GitHub Access using PAT, enter the PAT you created from that step. And, as with the OAuth example, click the Submit button to accept the changes.

If there is some reason to change the OAuth Client ID and Secret or change your PAT, you can get back to this window using the Settings icon , on the top banner.

Once access to your GitHub account has been authorized, you will now see all of your available GitHub projects. You can scroll down through the page to see all of your repositories:

If you have a large number of repositories, you can use the search field to find desired repositories. In the example below, typing in the characters "ba" will reveal 2 projects which contain that substring:

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 icon is to the right of the project name box.

NOTE: Once a repository has been cloned, it will jump to the top of the list of available repositories. This makes it more convenient to access a cloned repository later.

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 icon is replaced by Remove icon . 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: