Hi.

You want to work with branches. While PB does support branching, this functionality was introduced in PB 2019 R3. As you are using PB 2017, you cannot take advantage of this change.

So, I don't think you can do what you want using PB 2017.

Andreas.

Here is a link to information about using Git source control system in PB 2019 R3:

    https://docs.appeon.com/pb2019r3/pbug/ch01s03.html#Using_Git_source_control_system

The same chapter/section is present in the User's Guide documentation, updated for all later versions of PB to reflect the ever-evolving support for Git.

Once a PB workspace is prepared for git you can use any git feature, even if PB does not support it internally. To do that, follow the steps described in "Add a workspace to git". This will export all source code files from your PBLs to a folder called "ws_objects" so git can track them.

From this point on, the only internal PB feature related to git you absolutely need to use is "Refresh", which updates the actual PBLs with the current source code from ws_objects. Everything else can be done with an external git client of your choice. I prefer the command line interface myself.

I would recommend not commiting PBL changes because they are binary files and will lead to conflicts every time you try to merge them. Only add and commit new PBLs and the actual source code files, use "Refresh" to update PBLs after switching branches etc.