VERSION CONTROL Window

The VERSION CONTROL window, located in the Cross Function Area at the lower screen border, enables the integration of the version control systems SVN and Git into PLCnext Engineer. Here, a VCS can be selected and various repository-related functions are provided.

You can hide/show the window by clicking the button shown left on the Cross Function Area toolbar.
For closing the window, you can also click the cross icon on the right of the window title bar:
How to pin/unpin the window in the Cross Function Area

You can open several windows in the Cross Function Area at the same time by pinning them. Only if pinned, a window remains visible when another window is opened. If a window is unpinned, it is closed when you open another window.

To pin/unpin a window, click the pin icon in the upper right window corner. Unpinned windows show horizontal pin icon , pinned windows show the icon .

How to undock/dock the window /

By clicking the 'Undock' icon in the window title bar, the window can be undocked from the user interface and placed anywhere on the screen (or on a second screen, if available).

To insert it at its original position, click the 'Dock' icon .

Further Info
For detailed information about the VERSION CONTROL window and how to work with it, see the topic "Version Control System".

Toolbar Tab 'Tool'

Icon Command Description SVN/Git Command

-- 'Version control' drop down list Selects the VCS used. n/a

Create repository Creates a repository for the VCS selected. A new repository can only be created in an empty folder.
The repository can be created on a local or network folder. n/a

Get working copy Creates a working copy by checking out data from the repository. A dialog appears where you have to select the repository and set an empty working folder. SVN: Checkout

Git: Checkout

Icon	Command	Description	SVN/Git Command
--	'Version control' drop down list	Selects the VCS used.	n/a
	Create repository	Creates a repository for the VCS selected. A new repository can only be created in an empty folder. The repository can be created on a local or network folder.	n/a
	Get working copy	Creates a working copy by checking out data from the repository. A dialog appears where you have to select the repository and set an empty working folder.	SVN: Checkout
Git: Checkout

Toolbar Tab 'Pending Changes'

Icon Command Description SVN/Git Command

Refresh Refreshes the list of pending changes and sets the number of visible list entries. SVN: Refresh (in Repo browser)

Git: n/a

Commit Sends the modifications you made to your working copy to the repository (check-in).
Make sure that your working copy is up to date prior to commmitting (using the 'Update' (with SVN) or 'Pull' (Git) command).
Note that with Git, the revision is committed to the local repository and have to be pushed to the public main repository later (see 'Push' below). SVN: Commit

Git: Commit

Push Transfers data from your local Git repository to the public master repository.
Pushing is necessary for synchronizing several local repos with the master repository thus integrating the local modifications of each user.
Afterwards, other users can pull modifications into their local repository and working copy (see 'Pull' below). SVN: n/a

Git: Push

Update Updates your local working copy with changes that other users committed to the SVN repository.
The command checks the repository for updates (compared to your working copy) and, if available, merges them into your working copy.
Any modifications you made in the affected files are kept.
The repository is not changed by the 'Update' command. SVN: Update

Git: n/a

Revert Discards all pending changes and reverts the project to the revision which was committed last. SVN: Revert

Git: Revert

Pull Checks the public master Git repository for differences (updates compared to your working copy) and merges them into your local Git repository and into your working copy.
Such updates are necessary if the public master repository contains commits of other users.
Any modifications you made in the affected files are kept.
The public master repository is not changed by the 'Pull' command. SVN: n/a

Git: Pull

Icon	Command	Description	SVN/Git Command
	Refresh	Refreshes the list of pending changes and sets the number of visible list entries.	SVN: Refresh (in Repo browser)
Git: n/a
	Commit	Sends the modifications you made to your working copy to the repository (check-in). Make sure that your working copy is up to date prior to commmitting (using the 'Update' (with SVN) or 'Pull' (Git) command). Note that with Git, the revision is committed to the local repository and have to be pushed to the public main repository later (see 'Push' below).	SVN: Commit
Git: Commit
	Push	Transfers data from your local Git repository to the public master repository. Pushing is necessary for synchronizing several local repos with the master repository thus integrating the local modifications of each user. Afterwards, other users can pull modifications into their local repository and working copy (see 'Pull' below).	SVN: n/a
Git: Push
	Update	Updates your local working copy with changes that other users committed to the SVN repository. The command checks the repository for updates (compared to your working copy) and, if available, merges them into your working copy. Any modifications you made in the affected files are kept. The repository is not changed by the 'Update' command.	SVN: Update
Git: n/a
	Revert	Discards all pending changes and reverts the project to the revision which was committed last.	SVN: Revert
Git: Revert
	Pull	Checks the public master Git repository for differences (updates compared to your working copy) and merges them into your local Git repository and into your working copy. Such updates are necessary if the public master repository contains commits of other users. Any modifications you made in the affected files are kept. The public master repository is not changed by the 'Pull' command.	SVN: n/a
Git: Pull

Toolbar Tab 'History'

Icon Command Description SVN/Git Command

Refresh Refreshes the history list and sets the number of visible list entries ('Next 100' or 'Show All'). SVN: Refresh (in Repo browser)

Git: Refresh in Show log

Export revision Exports the revision marked in the history list into a directory. The project is exported in *.pcwef format. SVN: Export (in Windows Explorer context menu or Repo browser)

Git: Export this revision (in 'Log messages' window TortoiseGit)

Revert to revision Reverts the current project to the revision marked in the history list.
After reverting, the current project usually has pending changes. These pending changes can be commited or reverted on the 'Pending Changes' tab (using the 'Revert' command). SVN: Revert to this revision (in 'Log messages' window TortoiseSvn)

Git: Reset 'master' to this (in 'Log messages' window TortoiseGit)

Command	Description	SVN/Git Command
Refresh	Refreshes the history list and sets the number of visible list entries ('Next 100' or 'Show All').	SVN: Refresh (in Repo browser)
Refresh		Git: Refresh in Show log
Export revision	Exports the revision marked in the history list into a directory. The project is exported in *.pcwef format.	SVN: Export (in Windows Explorer context menu or Repo browser)
Export revision		Git: Export this revision (in 'Log messages' window TortoiseGit)
Revert to revision	Reverts the current project to the revision marked in the history list. After reverting, the current project usually has pending changes. These pending changes can be commited or reverted on the 'Pending Changes' tab (using the 'Revert' command).	SVN: Revert to this revision (in 'Log messages' window TortoiseSvn)
Revert to revision		Git: Reset 'master' to this (in 'Log messages' window TortoiseGit)