Add SVN or Git source control to your project.
Register model files as binary
Configure SVN, register model files, lock files, share repositories, and manage SVN externals.
Configure Git, register model files, add Git submodules.
To share your Simulink project, make your project publicly available on GitHub®.
Disable source control to prepare a project template.
Archive a project and create a new one with a different source control.
Use the Software Development Kit (SDK) to integrate Simulink Projects with third-party source control tools.
Use the MATLAB® Comparison Tool for diff and merge from external source control tools.
Get files from an SVN repository or clone a Git repository.
With SVN, tag specific revisions of a project.
Check for locally modified project files.
Find out if the repository version has moved ahead.
Update revisions with SVN or Git.
With SVN, ensure users get locks on model files before editing.
Examine changes in the project.
Review changes in modified files by comparing with ancestors, or compare particular revisions.
Check projects for problems such as unsaved changes, files not under source control, or derived files out-of-date.
Commit a change set to the repository (SVN) or local repository (Git).
Discard local changes or choose a revision for a file or the whole project.
Git workflow for fetching, merging and pushing changes to the remote repository.
Create, switch, merge, revert, and delete branches.
Locate and resolve conflicts; merge text files and merge models; extract conflict markers.
Use Simulink Project tools to migrate models to SLX and maintain revision history.
Best practices for derived files, such as
What source control tools and workflows can I use in Simulink Project? Try built-in SVN or Git, or integrate third-party tools.