Integrating with Git
Go Up to Main Page
Beginning with ER/Studio Data Architect 20.3, you can deploy a Devops process by integrating Data Architect with your Git repository. There is a brief video demonstrating this functionality. This feature allows you to commit CREATE DDL to your Git repository as well as use the Compare/Merge functionality to compare models with previous versions of that CREATE DDL in your Git repository. You can get started in setting up your Git integration by clicking the Git Options button in the Tools menu. You must be in the Physical Model view for this option to appear.
Data Architect works with the following Git implementations
- GitHub
- GitLab
- Atlassian Bitbucket
- Azure Repos
- Assembla
Clicking Git Options opens the Git Integration window.
Complete the following fields in the Git Integration window:
- Server URL. Type the https URL required for cloning or updating a particular repository.
- User Name. Type the name of the user account necessary to access the repository.
- Password / Personal Access Token. Type the password or token corresponding to the user accounts entered in the previous field.
- Location. Type or browse for the local Git repository that you want to clone or update.
- Enable warning before discarding uncommitted changes. Check this box to turn on warnings that appear while reverting local changes. Whenever an operation is performed to generate a database (.sql file) or compare and merge, ERDA "cleans" the repository by pulling the latest changes remotely. This action means that any local changes not committed and pushed are discarded.
- Test. Click this button to verify the entered credentials. You must successfully test your information before the Clone / Update button activates.
- Clone / Update. Use this button to fetch changes from the remote repository into the local repository. This button is inactive until after you test your entries.
Note: ERDA can update the repository only if the URL used to clone it matches the server URL provided in this window. Otherwise the repository is treated as a separate repository and ERDA does not allow the update.