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 6a3155926e first il y a 6 mois
..
.Resources first il y a 6 mois
Documentation~ first il y a 6 mois
Editor first il y a 6 mois
Lib first il y a 6 mois
.signature first il y a 6 mois
CHANGELOG.md first il y a 6 mois
CHANGELOG.md.meta first il y a 6 mois
Editor.meta first il y a 6 mois
LICENSE.md first il y a 6 mois
LICENSE.md.meta first il y a 6 mois
Lib.meta first il y a 6 mois
README.md first il y a 6 mois
README.md.meta first il y a 6 mois
Third Party Notices.md first il y a 6 mois
Third Party Notices.md.meta first il y a 6 mois
ValidationConfig.json first il y a 6 mois
ValidationConfig.json.meta first il y a 6 mois
package.json first il y a 6 mois
package.json.meta first il y a 6 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 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.