Git version control
Adeptia's Git version control capability lets you link your integration projects to a Git repository, so that project assets can be versioned as part of your integration lifecycle.
What you can do
By mapping a project to a Git repository, you connect an Adeptia project to a specific repository location, including the branch and file path where project assets reside. Each mapping connects one of your Adeptia projects to a specific Git repository. You can view the details of any existing mapping, edit it as your repository or credentials change, or remove it when it is no longer needed.
Where: My Company > Project Gi Mappings
What you configure
When creating or editing a project Git mapping, you provide the following information:
| Field | Required | Description |
|---|---|---|
| Project | Yes | The Adeptia project you want to link to a Git repository. |
| Import Git Config | No | Optionally copy the Git configuration from another existing project mapping, pre-filling the repository details below. |
| Repository URL | Yes | The web address of the Git repository. Must be a valid HTTP or HTTPS URL. |
| Username | No | The username used to authenticate with the repository. |
| Password or personal access token | No | The credential used to authenticate with the repository. |
| Branch name | Yes | The branch in the repository that the project will be mapped to. |
| File path | Yes | The path within the repository where the project assets are located. |
Testing your connection
After filling in the repository details, you can use the Test button to verify that the connection to the repository is valid before saving. The test uses the values currently entered in the form, and the button is available only when all required fields contain valid input.
Viewing a mapping
Selecting an existing mapping opens a detail view showing the project name, mapping identifier, repository URL, username, branch name, and file path. The password or personal access token is not displayed in plain text in this view.