Using a private VCS

As introduced in Authenticating GitHub Access with a Private VCS Repository, you may be using a locally deployed version of your VCS. Continuing to use GitHub as the example, here is how you set up to review repositories managed by GitHub Enterprise. If you are using GitLab Enterprise as your local VCS, refer to Authenticating GitLab Access with a Private VCS Repository for details on how to configure it for use with the Navigator.

This will bring up the window showing all of the private repositories that you may have configured. In our example, this will be the very first GitHub Enterprise server to be configured. So, the list of current servers is empty.

This brings up the configuration window where you set up the entries needed to locate the server and authenticate it with your OAuth credentials.

Set the name to anything you like. In this example we’ll call it “Private GitHub”.

Then, insert your URL to your private GitHub Enterprise Server. For our example, we have created a URL named vcs3.openrefactory.com. Note that you must add the https:// prefix to the URL to reach your server properly.

Finally, from the OAuth setup described in Authenticating GitHub Access with a Cloud-Based VCS Repository, you created a new Client ID and Secret key. Copy those from that window and paste them here.

Once the credentials are set, you may use that private repository by re-selecting GitHub Enterprise from the Select Repository pull-down menu. You will now see the display of all available private repositories. In our example here, you will see the one we just added: Private GitHub.

To see all of the repostiories on that Enterprise server, click on Get Repos to tell the Navigator to fetch all of the repositories associated with the currently logged in user to that private Enterprise server.

For our example, we have already loaded Baritone, our test project, there.

From here, everything works the same as outlined in Selecting your branch.