Skip to main content

View: Git Remotes

Symbol: _git_icon_remotes.png

Corresponding Git command: git remote

Function: The view is used to manage the remote repositories, which are used to manage CODESYS projects on where multiple users should be able to work. Local repositories of individual users can establish a link to a shared remote repository and synchronize/merge their commits there.

Important

Make sure you have a secure connection to a remote server. For more information, see: Security for CODESYS Git

Call: Git → Remotes menu

Requirement: A project is open and managed in Git.

_git_icon_refresh.png

The view is refreshed.

_git_icon_add_remote.pngAdd

Opens the Add new Remote dialog to specify the remote repository with which the CODESYS project should be linked

Alias name

Note: The usual name in Git for the remote repository is origin.

URL: URL or file path of the remote repository

The following protocols are currently supported: HTTP, HTTPS, local.

Examples: file:///D:/GitRep/Remote/<repository name>, https://dockerhostpde/testuser1/publicproject.git

_git_icon_delete_remote.pngRemove

The user is prompted whether to remove the link to the remote repository from the project.

Note: All remote branches that belong to the deleted remote repository are deleted. The local branches are retained, but no longer track the deleted remote branches. This action cannot be undone.

_git_icon_rename_remote.pngRename

The Alias name of the remote repository can be changed.

_git_icon_set_url.pngSet URL

Opens the Set URL for Remote <remote> dialog

Here, the path specification (URL or file path) for the currently used remote repository can be changed.

Changing the path information and therefore the link to the remote repository can cause remote branches to disappear. Therefore, the user has to reassign the mappings from local branches to remote branches (tracking). The local branches are not changed.

_git_icon_fetch.pngFetch

_git_icon_fetch.png Fetch (prune)

The local representative of the remote repository (example: origin/master) is updated with the status of the remote repository used by all users. All changes are applied from the remote repository. These are all new branches and new commits in the remote branches. However, the commits are not applied to the tracking branches.

Note: To update a local branch with the current status from the remote branch, a Pull operation also has to be performed in the Git Branches view.

As an option, you get the Fetch (prune) command by means of the _cds_icon_arrow_down.png button. This fetch command has the effect that remote branches which no longer exist in the remote repository are deleted from the local repository.

edit_credentials.pngCredentials

The button opens the Edit Credentials dialog. The User name and Password for access to the remote repository can be specified and edited here.

For the selected remote repository (remote name), the list box provides every URL for which the repository can provide credentials. The credentials for the selected URL can then be saved, deleted, or changed. It is recommended that you store the credentials for the first URL in the list box because they can then also be reused for other projects within the "domain". For detailed information about handling domain-specific credentials, see: Credentials needed.

Editing in the dialog replaces the editing in the Windows Credential Manager.

Note: A PAT (personal access token) is required when working with GitHUb. Then the PAT has to be specified instead of the password. Example of a PAT in GitHub: ghp_WPZP1ijlX4E<xxxxxxxxxxxxxxxxxx>

Table

Name:

Alias name of the remote repository

URL

URL or file path of the remote repository

: