Hi Roy,

PB IDE git integration will NOT version control your PFC files because they live outside your PBW's root folder.

You need a separate PFC workspace and PFC target. That workspace allows PB IDE git integration to version control the PFC code.

HTH /Michael

This means: It doesn't work ?

How other people resolve this problem?

Hi Roy,

I tried this out on PB 2017 R3 #1858. It boils down to PB IDE managing Git repo as a feature of your PBW workspace. Anything inside workspace root folder is maintained under source control by PB IDE. Same goes for any other source control system.

Anything outside the PBW's root folder remains outside automated source control by PB IDE. You need a separate PBW workspace to enable automated source control by the PB IDE.

I have experimented with complex Git repo configs. I learned that trying to coerce the IDE into more complex setups gives me more manual work outside the IDE.

My example:

1. Current Git controlled workspace = C:\LearnPB\GitPilot\GitPilot.pbw
2. Referenced code "outside Git" = C:\LearnPB\OutsideGit\SomewhereElse.pbl
3. Workspace to manage "outside" code = C:\LearnPB\OutsideGit\OutsideFramework.pbw

HTH /Michael