Ingen beskrivning
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
unknown 6a3155926e first 6 månader sedan
..
.Resources first 6 månader sedan
Documentation~ first 6 månader sedan
Editor first 6 månader sedan
Lib first 6 månader sedan
.signature first 6 månader sedan
CHANGELOG.md first 6 månader sedan
CHANGELOG.md.meta first 6 månader sedan
Editor.meta first 6 månader sedan
LICENSE.md first 6 månader sedan
LICENSE.md.meta first 6 månader sedan
Lib.meta first 6 månader sedan
README.md first 6 månader sedan
README.md.meta first 6 månader sedan
Third Party Notices.md first 6 månader sedan
Third Party Notices.md.meta first 6 månader sedan
ValidationConfig.json first 6 månader sedan
ValidationConfig.json.meta first 6 månader sedan
package.json first 6 månader sedan
package.json.meta first 6 månader sedan

README.md

Unity Version Control Package

ReleaseBadge

This package provides an in-editor interface for teams to work with Unity Version Control (Unity VCS), our leading version control solution, directly in Unity.

Note this project is the natural evolution of the old Collaborate package, hence its name.

Documentation - Changelog - Yamato

Compatibility

The minimum supported version of the Unity Editor is 2020.3.48f1 LTS.

Windows and macOS are officially supported.

The solution is exclusively targeting .NetStandard 2.0, and will not work with the legacy Mono runtime.

Maintenance

This project is currently maintained by the VCS Ecosystem team (@vcs-ecosystem-team), part of UGS DevOps.

All suggestions and issues are very welcome in the Slack channel #devs-unity-version-control.

Development

For developers

Option 1: clone this repository out into the packages/ directory in a project.

Option 2: clone elsewhere and link with the packages/manifest.json file in the project:

"com.unity.collab-proxy": "file:/some/path/to/package"

To add testing support also add the testibles section to the manifest. Your manifest should look like this:

{
  "dependencies": {
    "com.unity.collab-proxy": "file:/some/path/to/package",
    ...
  },
  "testables": [
    "com.unity.collab-proxy",
    ...
  ]
}

For internal testers

Simply add the git url into the packages/manifest.json file:

"com.unity.collab-proxy": "git://git@github.cds.internal.unity3d.com:unity/com.unity.cloud.collaborate.git"

If you need a specific revisision:

"com.unity.collab-proxy": "git://git@github.cds.internal.unity3d.com:unity/com.unity.cloud.collaborate.git#<rev>"

If you need more information, read the Documentation for package dependencies from git.

Code style is as dictated in Unity Meta.