Repositories

A Unity Cloud project can contain multiple repositories. Repositories store your project’s code, files, and file revision history. Your repository can contain as many Unity Editor projects, or external projects, as you need. You can control who has access to your repositories.

To access your organization’s repositories for your current project:

  1. Sign in to the Unity Cloud Dashboard.
  2. Go to DevOps > Version Control > Repositories.

Important: We are currently updating the Version Control experience. If you don’t have the New experience banner in your Version Control navigation menu, your repositories belong to a UVCS organization rather than a Unity Cloud project. This means that the steps to access your repositories differ slightly from the instructions above:

  1. Sign in to the Unity Cloud Dashboard.
  2. Go to DevOps > Version Control > Organizations.
  3. Select the organization in which you want to view repositories.
  4. Open the Repositories tab.

On the Repositories page, you can search for repositories using the search box.

Settings

You can edit your repository settings in the dashboard.

Mergebots

Mergebots are a tool you can use to automate your merge processes. For more information refer to Mergebots.

Mergebot integrations

You can set up mergebots to automate integration processes such as builds or notifications. For more information refer to Mergebots integrations.

Repository tabs

Each repository in the Unity Cloud Dashboard has the following tabs:

File explorer

The File explorer is a collection of all the current files within your repository. You can view the current files for each branch or changeset.

File locks

Displays files that you lock at checkout to prevent merge conflicts. You can manage or configure lock rules in your settings.

Code reviews

When you work on your project in a branch or changeset, you can request a code review on your alterations. This allows others to access a diff of your changes and contribute. For more information, refer to Request a code review and Provide a code review.

Branches

A branch works as a parallel line of development. You can create a branch that acts like a copy of your main repository and make changes on the branch. This isolates your changes so developers can work simultaneously, until you’re ready to merge your changes into the main repository. For more information, refer to Branches.

Changesets

A changeset is a collection of changes, additions, and deletions of code within your project. You can use changesets to group these alterations to help you manage and track the work in your project.

Labels

A label is an identifying word that you can attach to a changeset. For more information, refer to create a label.

Attributes

An attribute is metadata that you can assign to branches, changesets, or labels in Unity Version Control. For more information, refer to create an attribute. For example, you can use attributes to indicate when a branch is ready to integrate, or that a branch is no longer necessary. For example, you can call this attribute ARCHIVED, and give it two values: false for when the branch is still in use, and true for when you want to remove the branch.