Git troubleshooting#

Git is in itself a very complex and powerful system that sometimes causes difficulties. In combination with external Git servers it can sometimes come to some mistakes, which are listed here.

A team member cannot join the Git repository#

This may be because the team member was added on the Git server. Besides Anchorpoint, you also need to invite him to your repository on GitHub, Azure DevOps, Gitea, etc. so that he has access to the data. If a member does not have access, Anchorpoint will display the name of the Git server where you need to add your team member in a message.

Azure DevOps#

In the case of Azure DevOps, we have created a tutorial. Remember to change your team member from “Basic” to “Stakeholder” so they can read and edit data in the repository.


Upload your team member to a repository. To do this, do the following:

  • Open your repository on

  • Click on Settings at the top

  • Click on Collaborators on the left.

  • Click on the Add people button. It is important that you use the same email that was used in Anchorpoint.

Known and fixed bug#

If no server name is given, it could be that you are either hosting your own Git repository (e.g. using Gitea), or that you ran into a bug in the 1.5.0 release that was fixed in the 1.5.1 release. In this case, simply recreate the Anchorpoint project and assign your members again.

Advanced Python Logging#

The Git integration in Anchorpoint is based on the Action System, which is written in Python. To get more information about errors in Git in general, you can activate the option Advanced Python Logging under Account Settings / Troubleshooting. This way much more information will be written to the Python console. The console is accessible via the shortcut CTRL-SHIFT-P.