Skip to main content
Normal and Fork Git models are only available on the Express and Enterprise Editions.
By default, new projects use the Simple Git Storage Model and are hosted on Prophecy-managed Git. This lets users develop projects without knowledge of Git or branching strategies. While this is sufficient for most users, advanced users may want to change the Git Storage Model during project creation to use a normal or forked Git repository. Git setup during project creation

Model comparison

The following table describes the different Git storage models and how they work.
Regardless of the Git storage model you choose, you’ll be able to use a Prophecy-managed Git repository or your own external Git repository to host your project code.

Simple Git Storage Model

As you move through the Simple versioning workflow in your project, Prophecy actually maps these actions to Git processes in the backend. In other words, actions like saving, publishing, and restoring changes trigger Git commands. This is possible because all Prophecy projects are hosted on Git, regardless of the project’s Git storage model. The following diagram explains what each versioning action does in Git. If you connect to an external Git provider (rather than use Prophecy-managed Git), you can view how each action in is reflected in Git as you work on your project. Simple Git The table below reiterates the diagram.

Delete branch copies

In projects that use the Normal or Fork per user Git storage model, Prophecy keeps a local copy of each branch that a user checks out. Project admins can delete these copies to free up storage. Deleting a copy never changes your Git repository, and a user can restore a copy later by checking out the branch again. To delete branch copies:
  1. Open the Metadata page from the left sidebar.
  2. Open the project.
  3. Open the Branches tab.
  4. Select the branches you want to delete.
  5. Click Delete selected.
  6. Review the branches in the confirmation dialog, then confirm the deletion.
The Branches tab summarizes the total number of branch copies, the storage they use, and how many haven’t been used in 30 or more days. For each branch copy, the table shows the author of the last commit, when the branch was last updated, its status, and its size. A branch copy can have the following statuses:
  • Active: The branch is a user’s current working branch.
  • Uncommitted: The branch copy has changes that haven’t been committed. Deleting the copy discards these changes.
You can’t delete a user’s current working branch or the copy of the project’s main branch, which is labeled Default.