文档

Unity command-line interface (CLI)

Download Unity Hub

Unity command-line interface (CLI)

Version control commands for the Unity CLI

Manage version control for Unity projects with Git, Git providers, and Unity Version Control (UVCS), including commands for asset integrity checks, scene and prefab merges, resolving conflicts, and change analysis.
阅读时间22 分钟最后更新于 7 天前

Use the
unity vcs
commands to manage version control for Unity projects from the Unity CLI. Check repository health, track changes, compare scenes and prefabs, resolve merge conflicts, and analyze how changes affect assets, assemblies, and tests. The commands work with Unity Version Control (UVCS) and Git repositories, including GitHub, GitLab, and self-hosted Git with Git LFS. These commands are separate from Unity Collaboration.
Each command understands something about Unity projects that a generic version control tool doesn't. For example, scenes and prefabs are YAML ordered by serialization, a missing
.meta
file breaks every reference to its asset, and pulling with the Editor open can trigger a full reimport.

Command

Description

vcs setup
Sets up a project from no version control to its first commit on a remote. Asks only what it can't detect, and prints the equivalent flag command.
vcs providers
Reports which Git providers this machine can reach, as whom, and what each host allows.
vcs merge-setup
Configures Unity scene and prefab merging (UnityYAMLMerge) for the repository.
vcs doctor
Checks the repository settings, ignore rules, and LFS configuration a Unity project needs.
--fix
repairs what it can.
vcs hooks
Installs or removes Git hooks that run Unity integrity checks on your commits.
vcs status
Shows changes grouped by their meaning to Unity, including
.meta
file pairing problems.
vcs sync
Pulls safely: refuses while an Editor holds the project, fetches commits and LFS objects, then reports the reimport.
vcs switch
Switches branches safely and reports the impact before you switch.
vcs diff
Compares a scene or prefab by GameObject and component name rather than by
fileID
.
vcs blame
Shows who last changed each GameObject and component in a scene or prefab.
vcs guid
Shows which asset each GUID names, in your working tree or at a commit.
vcs summarize
Summarizes branch changes so you can paste them into a pull request.
vcs affected
Reports which assets, assemblies, and tests a change affects. Reports a lower bound when applicable.
vcs conflicts
Lists unresolved merge conflicts, classified by whether they can merge automatically.
vcs explain
Explains in plain language what each side of a conflict changed.
vcs resolve
Resolves a conflicted Unity asset using the Editor's own merge tool, or by taking one side.
vcs git
Git-only commands:
git migrate-lfs
and
git worktree
.
vcs uvcs
Unity Version Control reads:
uvcs locks
,
uvcs changesets
, and
uvcs review
.
Refer to
unity vcs <command> --help
for the complete list of options for each command.

Before you start

Choose the project

Commands that act on a project accept it in one of these ways, and use the current directory if you pass none:
  • A
    [path]
    argument: a project path or a registered project name.
  • The
    --project-path <path>
    option.
  • The
    UNITY_PROJECT_PATH
    environment variable.
Pass either the argument or the option, not both. Commands whose argument is a file, such as
vcs diff
,
vcs blame
,
vcs explain
, and
vcs resolve
, don't take
--project-path
. Neither does
vcs guid
, which reads the repository in the current directory and ignores
UNITY_PROJECT_PATH
.

Revisions

The
--from
,
--to
,
--at
, and
--since
options take a Git revision: a branch, a tag, a commit, or an expression such as
HEAD~3
.

Use text serialization

vcs diff
,
vcs blame
,
vcs explain
, and
vcs resolve
read text YAML. They report a binary-serialized asset as binary instead of returning an empty result. To get text assets, set Asset Serialization Mode to Force Text in Project Settings > Editor.
vcs doctor
reports this setting as
SERIALIZATION_NOT_FORCE_TEXT
.

Output for scripts

Every
vcs
command supports the CLI's output formats. Use
--json
(or
--format json
) when a script reads the result. For details, refer to Output formats and automation.

Set up version control

Put a project into version control and push its first commit. The command detects what it can, such as an existing repository or remote and the providers you're signed in to, and asks only what it can't work out. It adopts a Git repository that already has a remote.
unity vcs setup [options] [path]

Setup options

Option

Usage

Description

--vcs <provider>
--vcs github
The provider:
github
,
gitlab
,
uvcs
, or the host name of a self-hosted server.
--git-namespace <name>
--git-namespace my-studio
GitHub organization or GitLab group. Defaults to the signed-in user.
--git-repo <name>
--git-repo space-game
Remote repository name. Defaults to the project folder name.
--git-visibility <visibility>
--git-visibility internal
private
(default),
public
, or
internal
.
--git-default-branch <name>
--git-default-branch trunk
Default branch of a new repository. Defaults to
main
.
--git-remote-protocol <protocol>
--git-remote-protocol ssh
https
(default) or
ssh
.
--git-description <text>
--git-description "Space game"
Description of a new repository.
--git-token-from-stdin
--git-token-from-stdin
Reads a personal access token from standard input. Use this instead of
--git-token
in CI, where a command-line value is visible to other processes.
--no-initial-commit
--no-initial-commit
Skips the automatic first commit and push.
--git-lfs
--git-lfs
Initializes Git LFS before the first commit. New repositories only.
--vcs-region <name>
--vcs-region <region>
UVCS region for the organization's subscription, the first time only.
--dry-run
--dry-run
Shows what UVCS setup would create, then exits. Only with
--vcs uvcs
.
--cloud-org <id-or-name>
--cloud-org my-studio
Unity Cloud organization for UVCS. You can also set
UNITY_CLOUD_ORG
.
--cloud-project <id-or-name>
--cloud-project space-game
Existing Unity Cloud project to use with UVCS.
--preset <name>
--preset studio
Fills every option you don't pass from a saved preset.
--save-preset <name>
--save-preset studio
Saves this run's choices as a preset and makes it the default.
If you don't pass a token, the CLI looks for a Git credential in this order: the provider's environment variable, your Git credential helper or Git Credential Manager, then a provider CLI you're already signed in to (
gh
,
glab
, or
tea
). The CLI never signs you in or prompts for a token. If none of these has a credential, the command stops and names the sign-in command to run, so sign in to the provider CLI or pass a token first. UVCS uses your Unity sign-in (
unity auth login
) and needs no token.
If you pass
--git-lfs
and Git LFS isn't installed, the CLI prints the command that installs it with your platform's package manager. Run that command, then run
vcs setup
again. To have the CLI install Git LFS for you and continue, set
UNITY_INSTALL_MISSING_TOOLS=1
. On Linux, the installation asks for administrator rights.

Setup examples

# Run inside the project and answer the questionsunity vcs setup# Private GitHub repository in an organization, with Git LFS, without promptsunity vcs setup --vcs github --git-namespace my-studio --git-repo space-game --git-lfs --non-interactive# Self-hosted GitLab or Gitea, by host name, over SSHunity vcs setup --vcs git.example.com --git-namespace games --git-remote-protocol ssh# CI: read the token from a secret on standard inputprintf '%s' "$GITHUB_TOKEN" | unity vcs setup --vcs github --git-token-from-stdin --non-interactive# Unity Version Control: preview, then createunity vcs setup --vcs uvcs --cloud-org my-studio --dry-rununity vcs setup --vcs uvcs --cloud-org my-studio# Save the team's choices once and reuse them for every new projectunity vcs setup --vcs github --git-namespace my-studio --git-lfs --save-preset studiounity vcs setup --preset studio
To create a project and its repository in one step, use
unity projects create --vcs <provider>
.

Check provider access

Report the version control tools on this machine (
git
,
git-lfs
,
gh
,
glab
,
tea
, and the UVCS
cm
client), which providers the machine can reach and as whom, and what each host allows. This command makes network requests and never prompts for a credential.
unity vcs providers [--host <host>]...

Option

Usage

Description

--host <host>
--host github.example.com
Also reports this self-hosted GitHub, GitLab, or Gitea host. You can repeat it.
unity vcs providersunity vcs providers --host github.example.com --host gitlab.example.com

Configure scene and prefab merging

Configure Git to merge scenes and prefabs with
UnityYAMLMerge
, the merge tool every Editor installation includes. The command writes the
.gitattributes
entries and the merge driver configuration, then runs a test merge to prove the tool works.
unity vcs merge-setup [options] [path]

Option

Usage

Description

--editor-version <version>
--editor-version 6000.0.30f1
Uses this Editor version's merge tool instead of the version the project requires. You can also set
UNITY_EDITOR_VERSION
.
-e, --editor-path <path>
-e <editor path>
Uses the merge tool in this Editor installation.
--check
--check
Reports what needs to be configured without changing anything. Exits with code
4
when work remains.
--skip-verify
--skip-verify
Skips the test merge.
Git stores merge driver configuration in
.git/config
, which isn't committed. Run
vcs merge-setup
once in each clone, and use
--check
in CI to catch a clone that hasn't.
unity vcs merge-setupunity vcs merge-setup --check

Check repository health

Audit what a Unity project needs from its repository: Git settings, ignore rules, Git LFS patterns, and package pinning. The command exits with code
4
when it finds a problem.
unity vcs doctor [--fix] [--check <codes>] [path]

Option

Usage

Description

--fix
--fix
Repairs every repairable finding. Running it again changes nothing.
--check <codes>
--check GITIGNORE_MISSING,LFS_NOT_INSTALLED
Runs only these checks, separated by commas.

Doctor checks

Area

Checks

Ignore rules
GITIGNORE_MISSING
,
GITIGNORE_STALE
,
GITIGNORE_RULES_NEGATED
,
GENERATED_DIR_TRACKED
Meta files
META_FILES_IGNORED
,
META_FILES_HIDDEN
Attributes and settings
EOL_POLICY_MISSING
,
SERIALIZATION_NOT_FORCE_TEXT
Git LFS
LFS_NOT_INSTALLED
,
LFS_HOOKS_MISSING
,
LFS_PATTERNS_INCOMPLETE
,
LFS_PATTERNS_OVERRIDDEN
Packages
UPM_LOCK_UNTRACKED
,
UPM_LOCK_DRIFT
,
UPM_GIT_REF_FLOATING
,
UPM_GIT_REF_UNVERIFIED
Package submodules
UPM_SUBMODULE_UNINITIALIZED
,
UPM_SUBMODULE_DRIFTED
,
UPM_SUBMODULE_LFS_UNFETCHED
unity vcs doctorunity vcs doctor --fixunity vcs doctor --format github # annotations in a GitHub Actions log
vcs doctor
checks the repository's configuration. To check the integrity of the project's assets, use
unity projects verify
.

Install Git hooks

Install
pre-commit
,
post-checkout
, and
post-merge
hooks that run the Unity integrity checks automatically.
install
also upgrades hooks from an earlier version.
uninstall
removes only the block the CLI added, so your own hook content stays.
unity vcs hooks install [path]unity vcs hooks status [path]unity vcs hooks uninstall [path]

Show changes

Show what changed, grouped by what it means to Unity, with
.meta
file problems called out. For example, an asset added without its
.meta
file, or a
.meta
file left behind by a move. This command works only in a Git repository. In a UVCS workspace, use
unity uvcs status
for changes and
unity vcs uvcs locks
for lock state.
unity vcs status [path]

Pull changes safely

Pull commits and Git LFS objects, then report the reimport the pull causes. The command refuses while an Editor has the project open, because pulling under a running Editor can trigger a large reimport or corrupt the
Library
folder.
unity vcs sync [options] [path]

Option

Usage

Description

--rebase
--rebase
Replays your local commits on top of the incoming ones.
--allow-dirty
--allow-dirty
Pulls over uncommitted changes to tracked files instead of refusing.
--force
--force
Pulls even while an Editor has the project open.
--verify
--verify
Checks the project afterwards without asking.
unity vcs syncunity vcs sync --rebase --verify

Switch branches safely

Switch branches with the same Editor check as
vcs sync
, then report the reimport the switch causes.
unity vcs switch [options] <branch> [path]

Option

Usage

Description

--dry-run
--dry-run
Runs every check and reports the reimport scope without switching.
--allow-dirty
--allow-dirty
Carries uncommitted changes across the switch.
--discard-changes
--discard-changes
Discards uncommitted changes to tracked files.
--close-editor
--close-editor
Asks the Editor that has the project open to quit, then switches.
--force
--force
Switches even while an Editor has the project open.
-y, --yes
-y
Answers yes to every confirmation.
unity vcs switch feature/lighting --dry-rununity vcs switch feature/lightingunity vcs switch main --close-editor

Compare a scene or prefab

Show what changed in a scene, prefab, or other text-serialized asset, by GameObject and component name instead of by
fileID
. For example:
Changed Transform on Player at Player: position position: {x: 0, y: 0, z: 0} to {x: 5, y: 0, z: 0}
unity vcs diff [--from <revision>] [--to <revision>] [--full] <path>

Option

Usage

Description

--from <revision>
--from main
Revision to compare from. Defaults to
HEAD
.
--to <revision>
--to HEAD
Revision to compare to. Defaults to your working tree, including uncommitted changes.
--full
--full
Shows every change and every value in full, with no output limit.
Each changed object reports how confidently it was matched between the two revisions. Treat anything below
exact
as likely rather than certain. Prefab overrides are reported on the prefab instance in the referencing scene, not on the source prefab.
When a changed value refers to another asset, the output names that asset by its path, looked up at the commit on each side of the comparison. A label marks references that aren't an ordinary asset in the repository:
(added in this range)
,
(deleted in this range)
,
(built in)
,
(package)
,
(in this file)
, or
(not in this repository)
. In JSON, each value has
fromReferences
and
toReferences
. In objects larger than 4 MB, reference names appear only with
--full
. Without it, the output says the names were left out, and JSON sets
referencesTruncated: true
.
# Your uncommitted changes to a sceneunity vcs diff Assets/Scenes/Level.unity# What a branch changed in a prefabunity vcs diff Assets/Prefabs/Player.prefab --from main --to feature/jump# The last commit onlyunity vcs diff Assets/Scenes/Level.unity --from HEAD~1 --to HEAD# The complete result as JSON, for a script or an AI agentunity vcs diff Assets/Scenes/Level.unity --full --json > level-diff.json

Find who changed an object

Show who last changed each GameObject and component in a scene or prefab.
git blame
reports who last changed a line of YAML.
vcs blame
reports who last changed an object, such as the
Rigidbody
on the
Player
.
unity vcs blame [options] <path>

Option

Usage

Description

--at <revision>
--at v1.4.0
Blames as of this revision. Defaults to
HEAD
.
--object <name>
--object Player
Only this object, by name or hierarchy path. Naming a GameObject also returns its components.
--field <name>
--field m_Mass
Only the commit that last changed this serialized field.
--max-revisions <n>
--max-revisions 1000
How many revisions to search. Defaults to
200
.
If an object shows as
unknown
, the search reached
--max-revisions
before finding the change. Increase the limit and run the command again.
unity vcs blame Assets/Scenes/Level.unity# The Player and every component on itunity vcs blame Assets/Scenes/Level.unity --object Level/Actors/Player# Who last changed the Player's massunity vcs blame Assets/Scenes/Level.unity --object Player --field m_Mass

Find the asset a GUID names

Show which asset each GUID names. Logs, errors, and raw diffs often print a GUID instead of a path, and this saves searching every
.meta
file for it.
unity vcs guid [--at <revision>] <guid...>

Option

Usage

Description

--at <revision>
--at main
Looks the GUIDs up in the
.meta
files committed at this revision. Defaults to your working tree. Package GUIDs always come from the project's current
Library/PackageCache
folder, not from the packages that revision used.
The output has one row per GUID, in the order you pass them, with the GUID, its status, its path, and its name. The status is
present
,
built-in
,
package
, or
not-in-repository
. A GUID that names nothing still gets a row and isn't an error. A value that isn't 32 hexadecimal digits is a usage error, with exit code
2
.
unity vcs guid 0123456789abcdef0123456789abcdef# As of a branchunity vcs guid 0123456789abcdef0123456789abcdef --at main# Several at once, as JSONunity vcs guid 0123456789abcdef0123456789abcdef fedcba9876543210fedcba9876543210 --json

Summarize a branch

Summarize what a branch changed, ready to paste into a pull request: counts by Unity asset category, plus the risks a reviewer needs to see. Risks include GUID changes that can break references, assets moved without their
.meta
file, binary files that can't be reviewed as text, and package manifest changes.
unity vcs summarize --since <revision> [--to <revision>] [--objects] [--full] [path]

Option

Usage

Description

--since <revision>
--since main
Required. Starts the summary at this revision's merge base with the end of the range.
--to <revision>
--to origin/feature/login
Ends the range at this commit instead of
HEAD
, so you can summarize a branch without checking it out.
--objects
--objects
Adds what changed inside each changed scene, prefab, and asset, object by object, the way
vcs diff
reports one file.
--full
--full
Removes the per-file output limits. Implies
--objects
.
The
path
can be any folder inside the repository, so the command also works from the root of a repository that contains several projects.
unity vcs summarize --since main# Summarize another branch without checking it outunity vcs summarize --since main --to origin/feature/login# Include what changed inside each scene and prefabunity vcs summarize --since main --objects# Write the summary to a file and use it as a pull request bodyunity vcs summarize --since main --format human --no-color > pr-summary.md

Find affected assets and tests

Report which assets, assemblies, and tests a change affects. The command follows two separate paths:
  • Assets: from each changed asset, through GUID references, to the prefabs that reference it and then to the scenes that reference those.
  • Assemblies: from each changed script, assembly definition, or assembly definition reference to its assembly, and then to the assemblies that reference it, including test assemblies.
The asset path doesn't feed the assembly path. A change to only scenes or prefabs lists affected assets, but no assemblies or test assemblies.
unity vcs affected [--since <revision>] [path]

Option

Usage

Description

--since <revision>
--since main
Compares against this revision's merge base with
HEAD
. Defaults to
HEAD
, which reports your uncommitted changes.
The result is a lower bound. Addressables groups,
Resources
lookups, assets loaded by name in code, and binary assets are real dependencies that a static reader can't find. JSON output includes
lowerBound: true
and a
holes
object that counts what the command couldn't read. Use the result to prioritize tests, not to skip them.
unity vcs affectedunity vcs affected --since main# The test assemblies a branch affects, one per lineunity vcs affected --since main --json | jq -r '.data.testAssemblies[]'

List merge conflicts

List every unresolved conflict, classified by Unity asset type, with whether each one can merge automatically.
unity vcs conflicts [path]
unity vcs conflicts# Only the conflicts that need a personunity vcs conflicts --json | jq -r '.data.conflicts[] | select(.mergeEligible | not) | .path'

Explain a conflict

Explain, in plain language and by object and component name, what each branch changed in one conflicted asset.
unity vcs explain <path>

Resolve a conflict

Resolve a conflicted asset by merging both sides with
UnityYAMLMerge
, or by taking one side. Run
vcs merge-setup
first.
unity vcs resolve [--merge | --ours | --theirs] [options] <path>unity vcs resolve --all [options]

Option

Usage

Description

--merge
--merge
Merges both sides with
UnityYAMLMerge
. This is the default.
--ours
--ours
Keeps your side of the file and discards theirs.
--theirs
--theirs
Keeps their side of the file and discards yours.
--all
--all
Resolves every conflict that can merge automatically. Use it instead of a path.
--editor-version <version>
--editor-version 6000.0.30f1
Uses this Editor version's
UnityYAMLMerge
.
-e, --editor-path <path>
-e <editor path>
Uses the
UnityYAMLMerge
in this Editor installation.
unity vcs resolve Assets/Scenes/Level.unityunity vcs resolve Assets/Prefabs/Player.prefab --theirsunity vcs resolve --all

Git-only commands

unity vcs git
contains commands that have no UVCS equivalent.

Find binaries for Git LFS

Find binary files already committed to history and print the
git lfs migrate import
command that moves them to Git LFS. The command never runs the migration itself, because migrating rewrites history.
unity vcs git migrate-lfs [--min-size <size>] [--after <date>] [path]

Option

Usage

Description

--min-size <size>
--min-size 5MB
Smallest file size to report, such as
500KB
or
5MB
. Defaults to
1MB
.
--after <date>
--after 2025-01-01
Scans only commits newer than this date, to save time on a large repository. Accepts a date or a relative time, such as
"6 months ago"
.
The printed command includes only the asset types that Unity projects usually store in Git LFS, plus the types the repository already tracks there. Other large files are listed but not included, so source code doesn't end up in Git LFS. Agree on the migration with your team before you run it, because everyone has to clone again afterwards.
unity vcs git migrate-lfsunity vcs git migrate-lfs --min-size 5MB --after 2025-01-01

Work in a second checkout

Create a Git worktree that's ready to open in minutes instead of after a full import: it has the right Editor version, a
Library
folder copied from the current checkout, and an entry in the Unity Hub project list.
unity vcs git worktree add [options] <branch> [path]unity vcs git worktree remove [options] <path>
worktree add
options:

Option

Usage

Description

--into <folder>
--into ../space-game-lighting
Where to create the worktree. Defaults to a folder next to the repository, named after the branch.
--seed <mode>
--seed full
How much of the
Library
folder to copy:
cache
(default),
full
, or
none
.
cache
skips
Library/PackageCache
, which the Package Manager refills from its global cache.
--install-editor
--install-editor
Installs the Editor version the branch needs instead of only reporting it. If the command can't ask for confirmation, it stops before creating anything, with exit code
2
. Add
--yes
to install without asking.
--no-register
--no-register
Leaves the worktree out of the Unity Hub project list.
--dry-run
--dry-run
Reports the plan without changing anything.
-y, --yes
-y
Answers yes to every confirmation.
If the branch doesn't exist, the command creates it from
HEAD
.
worktree remove
options:

Option

Usage

Description

--discard-changes
--discard-changes
Removes the worktree even though it has uncommitted changes.
--force
--force
Removes the worktree even while an Editor has it open.
--dry-run
--dry-run
Reports the plan without changing anything.
-y, --yes
-y
Answers yes to every confirmation.
unity vcs git worktree add feature/lighting --into ../space-game-lightingunity open ../space-game-lightingunity vcs git worktree remove ../space-game-lighting --yes

Unity Version Control commands

unity vcs uvcs
contains UVCS commands with stable output for scripts. The commands need the UVCS command-line client,
cm
. To install it, run
unity plugin install uvcs
.
To run any other
cm
command, use
unity uvcs <arguments>
, which passes the arguments to
cm
unchanged. For example,
unity uvcs lock list
or
unity uvcs shelve
.

List locks

Show who holds each lock, and which locks cover files you changed.
unity vcs uvcs locks [path]

List changesets

List recent changesets.
unity vcs uvcs changesets [--limit <n>] [path]

Option

Usage

Description

--limit <n>
--limit 100
How many recent changesets to list. Defaults to
25
, up to
1000
.

Work with code reviews

Read, answer, and resolve UVCS code review comments.
vcs uvcs reviews
is an alias of
vcs uvcs review
.
unity vcs uvcs review [--changeset <id>] [--branch <name>] [--status <status>] [--limit <n>] [path]unity vcs uvcs review comments (--review <id> | --changeset <id> | --branch <name>) [--all-activity] [--limit <n>] [path]unity vcs uvcs review reply --review <id> --comment <id> --body <text> [path]unity vcs uvcs review resolve --review <id> --comment <id> --changeset <id> [path]

Subcommand

Description

(none)Lists code reviews, filtered by changeset, branch, or status. Lists up to 50 by default, and up to 500 with
--limit
.
comments
Lists a review's comments with the file and line each one refers to. Select the review by ID, or by the changeset or branch it belongs to.
--all-activity
also includes status changes and reviewer requests.
reply
Replies to a comment.
resolve
Marks a comment as applied in a changeset.
unity vcs uvcs reviews --branch /main/featureunity vcs uvcs review comments --review 42unity vcs uvcs review reply --review 42 --comment 7 --body "Fixed in the next changeset"unity vcs uvcs review resolve --review 42 --comment 7 --changeset 118

Common workflows

Put a new project under version control

unity vcs providersunity vcs setup --vcs github --git-namespace my-studio --git-lfsunity vcs merge-setupunity vcs hooks installunity vcs doctor

Set up a new clone

git clone https://github.com/my-studio/space-game.gitcd space-gameunity vcs doctor --fixunity vcs merge-setupunity vcs hooks install

Check a pull request in CI

Each command exits with a non-zero code when the repository needs attention, so the job fails.
set -euo pipefailunity vcs doctor --format githubunity vcs summarize --since "origin/$BASE_BRANCH" --format human --no-color > summary.mdunity vcs affected --since "origin/$BASE_BRANCH" --json > affected.json
The job doesn't run
vcs merge-setup --check
. The merge driver is stored in each clone's
.git/config
, which a fresh CI checkout never has, so the check would always fail there. Run
vcs merge-setup
once in each developer clone instead.

Resolve a merge that changed scenes

git merge feature/lightingunity vcs conflictsunity vcs resolve --allunity vcs conflictsunity vcs explain Assets/Scenes/Level.unityunity vcs resolve Assets/Scenes/Level.unity --theirsgit commit

Review a scene change

unity vcs summarize --since main --to origin/feature/lightingunity vcs diff Assets/Scenes/Level.unity --from main --to origin/feature/lightingunity vcs blame Assets/Scenes/Level.unity --object Sun --field m_Intensity --at origin/feature/lighting

Additional resources