Git Repository Issues
Common error messages and troubleshooting information when working with a Git repository in Oxygen Content Fusion.
This topic contains information about issues related to Git repositories.
Error When Importing a Project from Git
When using the Import from Git option to create a project in Content Fusion, the operation may fail with an error. In most cases, this is due to an incorrect configuration of the Git access token (or other credentials) used to connect to the repository. Content Fusion needs read and write permissions on the repository to clone it, create branches for review tasks, and commit changes. If the token has only read access (or no access to the repository), the import will fail. To resolve this, ensure that the access token is created with the correct scopes or permissions for your Git provider (GitHub, GitLab, Bitbucket, Azure DevOps).
For detailed steps and platform-specific requirements, see Creating Git Access Tokens for Projects.
User Not Authorized on Git Repository
User not authorized on Git repository
message when Content Fusion connects to your Git remote repository but the server rejects
the credentials or does not grant access to the repository URL you specified, there are
several possible causes:- Invalid or unusable credentials - Wrong access token or password, expired token, or token that was revoked or rotated.
- Insufficient permissions on this repository - The token is legitimate but does not have the read and write access Content Fusion needs on the repository from your clone URL . A read-only token can lead to authorization failures when pushing commits to the remote repository.
- Token limited to another repository - The token is tied to a different repository or to a fixed list that does not include the one you are importing (typical of fine-grained personal access tokens). Add the repository from your import URL to the token's permissions, or create a new token for that repository.