Repositories#

Repositories store your project’s code, files, and file revision history. Your projects can contain as many repositories as you need and you can control who can access each repository.

To access your organization’s repositories:

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. Select the Repositories tab.

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

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.

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 see 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 any object in Unity VCS. For more information, refer to create an attribute. For example, you can use attributes to indicate when a branch is ready to be integrated, or that a branch is no longer necessary. You could call this attribute ARCHIVED, and it will have two values: false for when the branch is still in use, and true for when you want to remove the branch.