| Key | Issue Type | Summary | Resolution | Note |
|---|---|---|---|---|
| GIT-1115 | Bug | Scripting: branch_set_upstream is named wrongly / provides wrong functionality |
Fixed | [[COMPATIBILITY_INFORMATION]] The git scripting functions "branch_set_upstream" are no longer supported, as they did provide logic of the git parameter "--set-upstream-to" instead of "--set-upstream". There is a new set of functions called "branch_set_upstream_to" with the same signatures, which provides the same functionality and matches the behavior of "--set-upstream-to". Currently, there is no scripting implementation of "--set-upstream", but one can use "branch_track" as it provides the same functionality for the majority of use cases. |
| GIT-1110 | Bug | All Git script driver functionalities, that cause a reload of the project require a VersionUpdateFlags parameter |
Fixed | [[COMPATIBILITY_INFORMATION]] From now on, the following functions have an additional parameter "update_flags" of type "VersionUpdateFlags": * GitScriptProject.branch_copy * GitScriptProject.checkout * GitScriptProject.discard_all_changes * GitScriptProject.merge * GitScriptProject.pull * GitScriptProject.resynchronize_project The introduction of this parameter was necessary to avoid the "Project Environment" dialog in noUI mode. The parameter is optional, and its default value is "VersionUpdateFlags.NoUpdates". To restore the previous behavior, calls of these functions have to set this parameter to "VersionUpdateFlags.Regular". |
| GIT-1105 | Bug | Resolving conflicts impossible, if Git repository path contains whitespaces or special characters |
Fixed | |
| GIT-1102 | Bug | Git repository connection sporadically lost when extracting project archive |
Fixed | [[GENERAL]] [[COMPATIBILITY_INFORMATION-OEM]] Projects which are stored under the same folder as those are created from TemporaryFileService and the temp folder from the windows user cannot be used with CODESYS Git |
| GIT-1048 | Improvement | Provide the user with detailed server certificate information, if automatic verification failed |
Fixed | [[GENERAL]] If automatic verification for a server certificate failed, the user now gets all information on the certificate to decide whether to accept it anyway or not. |
| GIT-1028 | Bug | Open history view throws an unhandled exception |
Fixed | |
| GIT-1027 | Bug | [ScriptDriver] API documentation for git.pull is missing |
Duplicate | [[GENERAL]] Duplicate to GIT-1025 |
| GIT-1026 | Bug | Exception after disconnecting project from git |
Fixed | |
| GIT-1025 | Bug | Scripting API: Parameter description is missing |
Fixed | |
| GIT-1013 | Epic | Update to the newest libgit2sharp version v0.30.0 (or newer) |
Fixed | [[GENERAL]] LibGit2Sharp has been updated to V0.30.0.0. |
| GIT-1012 | Bug | Diff cannot be opened in history because of exception "'commitSha' cannot be null or whitespace" |
Fixed | |
| GIT-1011 | Bug | Diff viewer cannot be opened in Git History view |
Cannot Reproduce | |
| GIT-1008 | Bug | Git operations via scripting may fail because of missing license |
Fixed | |
| GIT-910 | Improvement | MergeViewer: Make "Apply" more robust |
Fixed | |
| GIT-906 | Bug | Unhandled exception after removing remote |
Cannot Reproduce | |
| GIT-901 | Bug | Git status overlay continuously changes for renamed object |
Fixed | |
| GIT-896 | Bug | When opening a project with insufficient FS access rights, Git connection is lost |
Fixed | [[KNOWN_LIMITATIONS]] If a project connected to git is loaded by a user with fewer rights on the file system representation or the repository than the user who created the repository, the project may lose its git connection. As this issue is caused by the access rights of the single users on the file system, this issue cannot be solved by CODESYS Git. Possible workarounds are: * restart CODESYS with user who created the git repository (recommended) * grant the necessary access rights to the current user and reload the project |
| GIT-874 | Improvement | Don't translate "ours" and "theirs" to improve legibility |
Fixed | |
| GIT-872 | Improvement | Make error message from InterlockDecisions meaningful |
Fixed | |
| GIT-276 | Improvement | Branch view, Status view: Show difference between remote and local tracking branches |
Duplicate | [[GENERAL]] Duplicates GIT-717 |