The workspace GitLab connection avoids configuring every new project by hand. Once OAuth authorization is saved, Maleus can create a repository in a chosen GitLab namespace or link an existing repository directly from the new-project form.
This integration supports GitLab.com and self-managed GitLab instances. GitHub appears in the catalog as Coming soon, but it cannot yet be connected at this level.
This is a GitLab connection at Maleus workspace level, not a connection to a strict GitLab "organization" entity. The default namespace can be a group or subgroup the authorized account can access.
Before you start
You must be a workspace admin. In GitLab, prepare an OAuth application with:
the instance base URL, such as https://gitlab.com, with no trailing path;
the Redirect URI supplied by Maleus;
the api scope;
the Application ID and Application secret.
The OAuth application can be created from user, group or administration settings in GitLab, depending on your installation and governance.
The GitLab account that authorizes the connection acts for the whole workspace. Prefer a dedicated service account with access only to the relevant namespaces and repositories.
Connect GitLab
Open Settings → Version Control.
Choose GitLab under Your providers.
Copy the Redirect URI shown by Maleus into the GitLab OAuth application and enable the api scope.
In Maleus, enter the Instance URL, Application ID and Application secret.
Click Save & authorize.
In the GitLab window that opens, sign in with the intended account and accept the authorization.
Allow pop-ups for Maleus if the browser blocks the OAuth window. Credentials are encrypted per workspace and the Application secret is never displayed again after saving.
Version Control centralizes the workspace's Git providers.
Set repository automation defaults
An active connection opens the Repository defaults section.
Enable Create a repository with every new project.
Choose the Default namespace where repositories will be created.
Choose a Default visibility supported by your GitLab instance, such as Private.
Changes are saved immediately. There is no Save button in this section.
The namespace and visibility become the defaults for every new repository.
What a project creator sees
When GitLab is connected, New project includes a Source control block with three choices:
Choice
Effect
Create a new repository
Creates an empty repository in the selected namespace and links it to the project.
Import an existing repository
Searches accessible GitLab repositories and links one. A repository already used by another project is marked In use.
No repository for now
Creates the project without a repository. One can be connected later under Settings → Git Repository.
Even when automatic creation is enabled, the project creator can choose another option before submitting the project.
The repository path, availability and visibility are checked before the project is created.
Repository creation is best-effort: the Maleus project remains created if GitLab refuses the operation. A toast reports the failure and setup can be completed later from the project's Git settings.
Re-authorize or disconnect
If GitLab revokes or expires the authorization, the page shows Needs re-authorization. Repository creation is then paused for new projects without affecting existing repositories.
Use Re-authorize to renew authorization with the intended GitLab account.
Use Disconnect from the page menu to remove the workspace connection.
Disconnecting GitLab does not delete any existing repository. Existing remotes stay attached to projects, but operations that relied on workspace OAuth authorization may fail until GitLab is reconnected. The automated workflow is no longer offered to new projects.
We use trackers, some operated by US-based providers, to measure interest in our offers. Cookie Policy
The workspace GitLab connection avoids configuring every new project by hand. Once OAuth authorization is saved, Maleus can create a repository in a chosen GitLab namespace or link an existing repository directly from the new-project form.
This integration supports GitLab.com and self-managed GitLab instances. GitHub appears in the catalog as Coming soon, but it cannot yet be connected at this level.
This is a GitLab connection at Maleus workspace level, not a connection to a strict GitLab "organization" entity. The default namespace can be a group or subgroup the authorized account can access.
Before you start
You must be a workspace admin. In GitLab, prepare an OAuth application with:
https://gitlab.com, with no trailing path;apiscope;The OAuth application can be created from user, group or administration settings in GitLab, depending on your installation and governance.
The GitLab account that authorizes the connection acts for the whole workspace. Prefer a dedicated service account with access only to the relevant namespaces and repositories.
Connect GitLab
apiscope.Allow pop-ups for Maleus if the browser blocks the OAuth window. Credentials are encrypted per workspace and the Application secret is never displayed again after saving.
Version Control centralizes the workspace's Git providers.
Set repository automation defaults
An active connection opens the Repository defaults section.
Changes are saved immediately. There is no Save button in this section.
The namespace and visibility become the defaults for every new repository.
What a project creator sees
When GitLab is connected, New project includes a Source control block with three choices:
Even when automatic creation is enabled, the project creator can choose another option before submitting the project.
The repository path, availability and visibility are checked before the project is created.
Repository creation is best-effort: the Maleus project remains created if GitLab refuses the operation. A toast reports the failure and setup can be completed later from the project's Git settings.
Re-authorize or disconnect
If GitLab revokes or expires the authorization, the page shows Needs re-authorization. Repository creation is then paused for new projects without affecting existing repositories.
Disconnecting GitLab does not delete any existing repository. Existing remotes stay attached to projects, but operations that relied on workspace OAuth authorization may fail until GitLab is reconnected. The automated workflow is no longer offered to new projects.