Here are some key concepts for new users:

Unity's cloud-based build service that enables you to build projects remotely, previously known as Unity Cloud Build.

A Unity project represents a game or app your Organization is developing. A project stores all the files related to your game or app, such as the asset and Scene files. See 2D or 3D projects.

You can add a Unity Editor project from a repository, or you can create a new Unity Editor project and connect to Unity Version Control. For more information, refer to Get started with UVCS via the Unity Hub.

Version control systems are software that help you track changes you make in your code over time. As you edit your code, you tell the version control system to take a snapshot of your files. The version control system saves that snapshot permanently, so you can recall it later if you need it. Use Unity Version Control to save your work and coordinate code changes across your team.

A repository is a location for your code managed by version control. You can store, manage, and develop source code with Unity Version Control. A Unity Cloud project can contain multiple Version Control repositories, and each repository can contain a single or multiple Unity Editor projects.

A collection of binaries and deployment manifests that are delivered to the target deployment environment. DevOps artifacts can be a container image, an instance group deployment configuration, or a generic artifact.

Defines a set of stages for the build process: building, testing and compiling software artifacts, and optionally triggering a deployment.

A sequence of steps for deploying a set of artifacts to a target environment. A deployment pipeline contains stages that run sequentially or in parallel.

Branches are lightweight references that keep a history of commits and provide a way to isolate changes for a feature or a bug fix from your main branch and other work.

A special file used in many Version Control Systems which specifies files to be excluded from version control. In Unity projects, several files can be excluded from version control. Using an Ignore File is the best way to achieve this. For more information, see the Version control best practices ebook.

Check in is the act of submitting changes to the repository. You must enter a comment in the text box before you can check in your changes.

Your workspace interacts with the version control, where you download the files and make the required changes for each check in.