Each project can be linked individually to an existing Git repository. Maleus can then push the project's code to it and use its branch as the starting point for deployments.
This setup is separate from the workspace GitLab connection, which automates repository creation or import when a project is created.
Before you start
Only admins can configure the connection. Prepare:
the repository's HTTPS URL;
the branch Maleus should push to, maleus by default;
a personal access token allowed to read and write that repository.
The form supports GitHub, GitLab, Bitbucket and Azure DevOps. The exact token permissions depend on the provider, but it must grant access to the target repository.
Use a dedicated token with only the permissions it needs. Maleus encrypts it when you save and never displays it again.
Open Git Repository settings
Open the relevant project.
Enter Settings.
Choose Git Repository in the sidebar.
With no configuration, the page shows No Git repository configured. Click Configure.
The repository is configured one project at a time from project settings.
Enter the repository details
Complete the Connect a repository form:
Choose the Provider.
Enter the Branch Maleus should use.
Paste the HTTPS Repository URL.
Paste the Personal Access Token.
Click Save.
The token stays blank on screen and must be entered again when editing the connection.
If saving fails, the form keeps the provider's error message together with a support reference. Check the URL, token permissions and branch existence first.
Check the connection and push
Once saved, the card shows the provider, URL, branch and Connected status.
Push to branch pushes the current project state to the configured branch. It requires an available development environment. The push result is shown directly in the card.
The connected card confirms the remote and branch used by the project.
Edit or remove the connection
The card menu offers:
Edit to change the provider, URL or branch. The token must be entered again;
Copy URL to copy the remote URL;
Remove to disconnect the project from the repository.
Removing the configuration does not delete the repository at the provider. The project stays in Maleus, but pushes and deployments that depend on the remote cannot run until a repository is connected again.
Next step
Once the repository is connected, configure the environments to which versions can be promoted in Configure deployment targets.
We use trackers, some operated by US-based providers, to measure interest in our offers. Cookie Policy
Each project can be linked individually to an existing Git repository. Maleus can then push the project's code to it and use its branch as the starting point for deployments.
This setup is separate from the workspace GitLab connection, which automates repository creation or import when a project is created.
Before you start
Only admins can configure the connection. Prepare:
maleusby default;The form supports GitHub, GitLab, Bitbucket and Azure DevOps. The exact token permissions depend on the provider, but it must grant access to the target repository.
Use a dedicated token with only the permissions it needs. Maleus encrypts it when you save and never displays it again.
Open Git Repository settings
With no configuration, the page shows No Git repository configured. Click Configure.
The repository is configured one project at a time from project settings.
Enter the repository details
Complete the Connect a repository form:
The token stays blank on screen and must be entered again when editing the connection.
If saving fails, the form keeps the provider's error message together with a support reference. Check the URL, token permissions and branch existence first.
Check the connection and push
Once saved, the card shows the provider, URL, branch and Connected status.
Push to branch pushes the current project state to the configured branch. It requires an available development environment. The push result is shown directly in the card.
The connected card confirms the remote and branch used by the project.
Edit or remove the connection
The card menu offers:
Removing the configuration does not delete the repository at the provider. The project stays in Maleus, but pushes and deployments that depend on the remote cannot run until a repository is connected again.
Next step
Once the repository is connected, configure the environments to which versions can be promoted in Configure deployment targets.