Integrating Control Room with Git repositories

Git integration with the Control Room ensures one-to-one mapping of the bots checked in to the public workspace of the Control Room and the remote Git file structure. Git commits enable you to enforce security, compliance, and code standards, and ensures that an organization's established best practices can be applied to their bot development processes.

The Control Room has Git Client that is connected to the Git repository that stores the file history of your public workspace. Each time a bot developer performs a bot check-in:

The bot and the dependent files are checked in to the public workspace.
The Control Room creates a commit that contains all the contents of the particular check-in within the Git repository.
The comment entered in the check-in process is used as the Git commit message and the user details are recorded as the author of the Git commit.
The Bot definitions are stored as JSON files in the Git repository.

Note: The Git repository must be configured to have write access only to the Control Room and not to any other Git client.

Supported Git repositories

You can configure the Control Room to replicate the built-in Git repository with the remote Git host, and synchronize information using Git push. The following sources are certified for Git integration with the Control Room.

GitHub
BitBucket
Azure DevOps

Configure HTTPS (username and password authentication) between the Control Room and the remote Git host. The Control Room and remote Git host use standard Git push protocol over HTTPS to send or receive data.

Exposing the files to your remote Git host enables you to review the bot code and files using third-party comparisons and static code analysis tools to help enforce compliance and maintain security standards.

Automation 360