Versioning projects with version control
Within a Neuron Power Engineer project, you can use an external source control tool, such as Git, to version your projects.
Git is a version control system that tracks different versions of files. On each computer working on a Git-controlled project, a local copy of the project is stored in a repository. Collaboration with other users is enabled through features that synchronize changes between the respective repositories. Typically, a central server hosts a repository containing a consolidated copy of the project. For details see the Git documentation.
|
Using Git requires appropriate experience and prior knowledge of source code management tools. |
The .gitignore file is manually created when the repository is set up. Typically, this is done outside of Neuron Power Engineer. By default, the .gitignore file is not displayed in the views containing the projects/resources. For details on how to display it, see the Good to know box in "Importing a project from the team server".
Neuron recommends that you clean the project when you check it out from Git.
Excluding files and folders from version control
In some cases, it may be useful to exclude specific files and folders from version control. When you commit your local changes to the server, the files and folders specified in the .gitignore file will be ignored.
The following example illustrates the files and folders excluded in the .gitignore file. Depending on the settings your system integrator has specified, your .gitignore file may differ from this example.
| Example of files and folders excluded in the .gitignore file |
|---|
|
The following files and folders are excluded in the .gitignore file because they are not part of the object identity checks. They are also included in the example above.
-
.log -
target -
oem-data -
libspecs -
.cproject