Skip to main content
Available for the Enterprise Edition only.
A Git connection policy restricts which external Git repositories can be accessed by Prophecy projects. The policy applies to every team and user in a given deployment.
Projects that use Prophecy-managed Git are never affected.

​
Prerequisites

To configure the Git connection policy, you must be logged in as a Prophecy administrator.

​
When the policy applies

Prophecy checks the policy only when a user connects a repository to a project, such as when they create a project with an external Git repository or connect an existing project to a different repository. Projects that are already connected to a repository keep working, even if the repository doesn’t comply with the policy.

​
Configure the policy

To configure the policy:
  1. Click the three dots at the bottom of the left navigation, then click the Settings icon.
  2. Open the Admin tab.
  3. Open the Git Connection Policy tab.
  4. In the Policy tab, configure the fields described below.
  5. Click Save policy.
When the mode is Allowlist, you must add at least one organization before you can save the policy. If any line in Allowed organisations isn’t valid, Prophecy shows the error for that line and skips it when you save.

​
Allowed organisation patterns

Each entry in Allowed organisations matches the path of a repository after the Git host. For example, the repository https://github.com/acme-data/pipelines-sales has the path acme-data/pipelines-sales. Matching is case-insensitive and compares whole path segments. For example, acme-data doesn’t allow acme-datastore. In a pattern, * matches any number of characters and ? matches exactly one character. Neither wildcard matches across a /.

​
What users see

When a user enters a repository that the policy doesn’t allow, Prophecy shows a message next to the repository that explains why and lists the allowed organizations.
  • If enforcement is Block (refuse), the user can’t connect the repository.
  • If enforcement is Warn (record only), the user can connect the repository, and Prophecy records the violation.

​
Review compliance

Open the Compliance report tab to see which existing projects use repositories that the current policy doesn’t allow. Projects that use Prophecy-managed Git aren’t listed. The report summarizes how many repositories violate the policy and lists the organizations currently in use. If you haven’t configured a policy yet, use this list to decide which organizations to allow. For each project, the report shows the following information. You can search the report and filter it by status or organization. Flagged projects keep working. The policy only applies when a user connects a project to a repository.