Skip to main content

Commit changes

This page describes how to commit your changes and create new branches from the main branch.

Commit changes into the dev branch​

When you create your first Project, dev/$USERNAME branch is automatically suggested for you to create. This is to ensure that no edits/commits are made directly on the main branch.

Within a Project, create a Pipeline and commit changes to the dev branch:

View code changes​

You can view the code changes of your commit when you start the process to commit changes. This gives you granular change visibility so that you can understand the detailed changes being made to your Pipelines, Models, datasets, and other entities.

View Git code changes

  • (A) Code Changes - The Code Changes tab shows all of the files with changes.
  • (B) Metadata changes - The Metadata changes tab shows all of the Prophecy metadata files with changes.
  • (C) Code changes - Toggling on Code changes allows you to view the code differences, with highlighted lines for additions and deletions.
  • (D) Reset - Clicking Reset allows you to revert the changes.
  • (E) Change files - This shows the total number of changed files and the number of added and delete lines.

Create or checkout a branch​

Currently we are on dev branch which has our first_Pipeline. Now let's see how to go back to our main branch and also create a new second_branch from the main branch.