Skip to main content

Git

Prophecy utilizes Git to align with DevOps practices. Git lets you:

  • Store your visual pipelines as code.
  • Track your project metadata, including workflows, schedules, datasets, and computed metadata.
  • Collaborate on your projects and perform code reviews.
  • Track changes across time.

Projects and Git repositories​

When you create a project in Prophecy, you must choose an empty Git repository or a path in a repository to host the underlying project code. This way, Prophecy can keep track of any changes to the project (including pipelines, models, datasets, and jobs) in a systematic way.

If you're unfamiliar with Git, or you don't need to connect to an external Git repository, you can connect your projects to Prophecy-managed repositories. To leverage the full functionality of Git, however, you need to connect your projects to external Git repositories. To do so, you need to add external Git credentials to Prophecy.

Add Git credentials to Prophecy​

When you create a project in Prophecy, You can either choose a Prophecy-managed repository or connect an external repository.

To add an external Git account to your Prophecy environment:

  1. Open Settings from the ellipses menu in the left sidebar.
  2. Select the Git tab. You will see any existing Git credentials here.
  3. Click Add new.
  4. Choose the relevant Git Provider and provide the following details:
    • An alias for your Git credentials.
    • Your Git email.
    • Your Git username.
    • Your Git personal access token (PAT). You should be able to find instructions on accessing your personal access token in each external provider's documentation.
  5. Click Connect to save the credentials.

You can also enter new Git credentials directly when creating a new project.

GitHub Oauth​

If you choose GitHub as your external Git provider, you can add your Git credentials using GitHub Oauth.

To use GitHub Oauth, a GitHub admin will need to authorize Prophecy to access the APIs required to access your organization's repositories. Follow the approval steps to set this up.

Fork per User​

When you create a project, you have the option to choose a single repository shared among users, or to Fork per User. When you Fork per User, every user gets their own fork of the repository.

When you fork a repository, you must already have both the upstream repository and a Fork per User repository present.

note
  • Changes made in forked repository do not affect the upstream repository.
  • Please follow the normal Git flow for raising pull requests to the original repository from the forked repository.

What's next​

Learn more about the Git workflow or try it yourself in Develop and deploy a project.