- HOW TO SET UP BITBUCKET ACCESS FOR TORTOISEGIT UPDATE
- HOW TO SET UP BITBUCKET ACCESS FOR TORTOISEGIT FULL
For more information on this, see Units Encoding.
HOW TO SET UP BITBUCKET ACCESS FOR TORTOISEGIT FULL
The dialogs of TortoiseGit have full support for non-latin characters. As a workaround, we recommend that you enable integration with the TortoiseGit client. Working with branches, tags and commit messages that contain non-latin characters may cause errors. TestComplete does not support non-latin characters in names of branches, tags, commit messages and other text labels.
HOW TO SET UP BITBUCKET ACCESS FOR TORTOISEGIT UPDATE
As a workaround, you can navigate to your submodules and add and update files there manually. It will ignore submodule changes when pulling changesets from repositories. TestComplete cannot work with bare Git repositories.Ĭurrently, TestComplete integration with Git does not provide support for submodules. See Source Control File Status Icons for detailed description of each icon: When the project suite or one of its projects is bound to a source code control system, the project item icons in the Project Explorer panel include small images that indicate the source control status of the files. Opens the Git Repository Settings dialog. Refreshes the status of items in the source control. Uploads your changes to the remote repository. Gets changes from the remote repository and merges them to your local repository. Submits your latest changes to the repository.įetches data about changes from the remote repository. Opens the Branches dialog that lists local and remote branches. Opens the history of changes made to the repository. Unbinds projects from the source control and deletes the repository. When Git integration is enabled, the Source Control menus and the toolbar contain the following items: ItemĬlones an existing repository that stores a project suite (or project) and then tries to open that project suite (project) in TestComplete.Ĭreates a local Git repository and adds the current project suite or project to this repository. Such items are typically added as part of their parent items. This means that the item is not stored in a file, so it cannot be added to a source control system as an individual instance. Note that the context menu of some items in the Project Explorer does not include the Source Control submenu. These menus and the toolbar hold the same items. Source Control menu and Source Control toolbar with Git integration enabled.