Hi,
I've been testing PowerBuilders built in source control for both GIT and something called SourceGear Vault. I'm hoping to see if anyone has any tricks or tips for utilizing the Source Control to its best ability, thanks!

Git

So far from what I've seen, it seems to work really well but two things I have come across that I wasn't able to figure out how to execute without using CMD. These two things are deletions and adding new files/modifications to files that aren't PowerBuilder files (.txt, .ini, .json). I have also noticed that when using GIT it doesn't push .PBL files with the rest of the push instead there is a separate option for this, is there a way to push the .PBL's at the same time it pushes other changes? I am pretty comfortable using git with only CMD, but would like to see if everything can be handled within the source control itself.

SourceGear Vault

I'm not sure if this has been used by anyone but when using this for the source control in PowerBuilder I have found a couple of things that make me question if I am working with this tool correctly. These things are:

• If you don't already have a local version of the project, you can't use PowerBuilder's built-in source control to check it out directly from SourceGear Vault. Instead, you have to manually pull the project from SourceGear itself.
• When checking files back in, PowerBuilder's console sometimes displays an error message, although it seems like the files are actually checked in correctly. This error seems misleading, as everything appears to be checked in as expected despite the warning.
• The workspace file (.pbw) and library file (.pbl) aren’t checked in or out. The .pbl is broken down into individual files. (Git behaves similarly but it gives you the option to check in the .pbl files as well). 
• There are a few visual bugs with file status updates, but these can be resolved by refreshing the System Tree.