This is machine translation

Translated by Microsoft
Mouseover text to see original. Click the button below to return to the English version of the page.

Note: This page has been translated by MathWorks. Click here to see
To view all translated materials including this page, select Country from the country navigator on the bottom of this page.

About Source Control with Projects

You can use a project to work with source control. You can perform operations such as update, commit, merge changes, and view revision history directly from the project environment.

In MATLAB®, projects have interfaces to:

Tip

You can check for updated source control integration downloads on the projects Web page: https://www.mathworks.com/discovery/simulink-projects.html

To use source control in your project, use any of the following workflows:

When your project is under source control, you can:

Caution

Before using source control, you must register model files with your source control tools to avoid corrupting models. See Register Model Files with Source Control Tools.

To view an example project under source control, see Explore Project Tools with the Airframe Project.

Classic and Distributed Source Control

This diagram represents the classic source control workflow (for example, using SVN).

Benefits of classic source control:

  • Locking and user permissions on a per-file basis (e.g., you can enforce locking of model files)

  • Central server, reducing local storage needs

  • Simple and easy to learn

This diagram represents the distributed source control workflow (for example, using Git).

Benefits of distributed source control:

  • Offline working

  • Local repository, which provides full history

  • Branching

  • Multiple remote repositories, enabling large-scale hierarchical access control

To choose classic or distributed source control, consider these tips.

Classic source control can be helpful if:

  • You need file locks.

  • You are new to source control.

Distributed source control can be helpful if:

  • You need to work offline, commit regularly, and need access to the full repository history.

  • You need to branch locally.

Related Topics