How to use GITHUB as source control in Pega?

Hi All,

Good day!

May we ask on how to use GITHUB as source control in Pega 8.3.0 instead of default check-in/check-out mechanisms?
Please provide the steps to use GITHUB as source control.

Reason: We have a project of deploying as well the Pega code in both DB tables and GITHUB repository in case that the DB rule tables have been corrupted, then we have a backup that we can able to retrieve in GITHUB.

Thank you in advance and More Power!


Keep up to date on this post and subscribe to comments

October 21, 2019 - 6:52am

Dear Felicita,


It's near to impossible to use git instead of checkin/-out rules process, because it's burned in Pega engine and one could not achieve that in a reasonable time and effort.

If you're afraid that your DB table will be corrupted (what're the reasons, btw, you foresee for that?), just do a full DB backup every week/day. In case of db corruption, you can roll everything back

October 21, 2019 - 11:53pm
Response to vaspoz

Hi Vaspoz,

Thank you for your reply. The reason why we need to use GITHUB because, this is one the requirements of the company to put the source codes/control in GITHUB.

If this is not possible, then we can consider to use the supported artifacts repository of Pega like JFrog Artifactory, Amazon S3 etc.

Thank you so much :)

October 22, 2019 - 11:36pm
Response to FeliA

You should definitely use a repository such as JFrog Artifactory especially as this is a repository manager which is the exactly intended to do what you have outlined. You do not need nor can you use a source control system such as Bitbucket or any other Git (similar) based source code version control systems as Pega itself does that through ruleset versioning and the layer cake concepts. See the answer to question 13 in the Deployment Manager FAQ which give a more detailed explanation and is applicable even if you are not using Deployment Manager