Git

The Git source configuration type is implemented as an external type.

Git is a free and open source distributed version control system.

To use Git as an artifact source, select Git from the Source Config Type drop-down list box and then configure the type-specific fields described here. For information about creating components, see Create components.

Git Fields Table

Field Description
Repository URL Enter the base URL for the Git repository.
Branch Enter the Git branch from which to get artifacts, such as main.
Watch for tags If selected, Deployment Automation watches for new tags instead of new versions.
Includes The patterns to match files to upload. The wildcard ** indicates every directory and * indicates every file. For example, dist/**/* retrieves the entire file tree under the dist directory.
Excludes The patterns to match files to exclude from the upload.
GIT Path Enter the Git client executable, using the full path if necessary. For example:

git
Preserve Execute Permissions If selected, file execute permissions are saved with the files.
Use Latest Component Properties for Version Download

If this is selected, the current component properties are used to download this component's version artifacts in Versions > Artifacts. You should deselect this if the component's storage location or connection details have changed since the version artifacts you want to download were imported, so that the component properties that were set when the version was created are used instead. For more details on maintaining versions externally, see Import component versions.
Copy to CodeStation

This option, selected by default, creates a tamper-proof copy of the artifacts and stores them in the embedded artifact management system, CodeStation. For optimal use of Deployment Automation, the check box should be selected.

If you deselect Copy to Codestation for this source configuration type, pointers to versions are saved in Deployment Automation rather than the versions themselves. This enables you to track the versions, but limits some functionality in Deployment Automation. For more details on maintaining versions externally, see Import component versions.