Hi.

I guess you are trying to connect using properties of workspace.

But Git & SVN are not available in that window. To add an existing project to git, you have to right click on your workspace, then, in popup menu that appears you have to select "Add to Source Control" option.

A new popup will show on with two choices: Git and Subversion (SVN). Choose Git. You will be prompted for your name and an email (those should match with those on your git server). After submitting that information, a local repository of your project will be created (you can add a comment for first commit, but this is optional).

When you complete above steps, open again workspace properties. Go to source control tab. You should see the information for git in a screen like the following:

Here you will have to fill missing information:

• User ID (for github in your case)
• Password/Token (I believe that you will have to create a token in github)
• Repository URL (you should create your repository in github, and put here it's url).

Also take a look at options available in advanced button (I suggest also to have TortoiseGit on your computer).

I strongly recommend you to read the following information from PB 2022 documentation:

Using Source Control - - Users Guide (appeon.com) and especially Using Git source control system - - Users Guide (appeon.com).

The documentation is good and the procedure is straight forward.

Andreas.

Thanks Andreas for the detailed response!

I don't have "Add to Source Control" in my workspace menu? Any idea what I'm missing?

you're not on the latest version of 2022 (R2), but I don't think that the "standard" version of PB won't let you connect to source control.

(If so, then that's a bug in my opinion).

What if you close your workspace and then rmb click on "no workspace" ? (PB2019 R3):

When choosing "Connect to Workspace" you should see something like this:

regards

Hi John,

Can you not see any menus related to SVN & Git in your environment, including the menu Connect to Workspace?

We saw a similar issue with another customer before. It was caused by a third-party source code management software in the customer's environment. After uninstalling it, the various menus of source code management in PB become normal.

Regards,

Kitty

Hi, we found the bug and reported it with our ticket. Wanted to close the loop here. In our ticket, Kitty He assured us in our ticket that: 

PB’s source control feature is not restricted by license type and all types of 
licenses have full access to the source control feature.

So we found that we could see the menu on our dedicated build machine. After discussing it in the ticket, we created a pristine virtual desktop and started from scratch. We couldn't see the menu even in that environment. We logged in as the build user and that had the same results. We started comparing INI files and config files, installed software to match the build machine and nothing worked. 

The person using the build machine does not regularly work in PB. All of our regular PB developers use the Library Painter. The Library Painter does not show the correct context menus. The guy on the build machine is using the System Tree. The Add to Source Control menu does show in the System Tree.