Aucune description
Vous ne pouvez pas sélectionner plus de 25 sujets Les noms de sujets doivent commencer par une lettre ou un nombre, peuvent contenir des tirets ('-') et peuvent comporter jusqu'à 35 caractères.
unknown 6f466a7c59 back il y a 9 mois
..
.Resources back il y a 9 mois
Documentation~ back il y a 9 mois
Editor back il y a 9 mois
Lib back il y a 9 mois
.buginfo back il y a 9 mois
.gitattributes back il y a 9 mois
.signature back il y a 9 mois
CHANGELOG.md back il y a 9 mois
CHANGELOG.md.meta back il y a 9 mois
Editor.meta back il y a 9 mois
LICENSE.md back il y a 9 mois
LICENSE.md.meta back il y a 9 mois
Lib.meta back il y a 9 mois
README.md back il y a 9 mois
README.md.meta back il y a 9 mois
Third Party Notices.md back il y a 9 mois
Third Party Notices.md.meta back il y a 9 mois
ValidationConfig.json back il y a 9 mois
ValidationConfig.json.meta back il y a 9 mois
package.json back il y a 9 mois
package.json.meta back il y a 9 mois

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 2021.3 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.