GitLab Integration
GitLab integration lets DBModeler push migration SQL into a GitLab repository using either a Personal Access Token or OAuth, depending on the configuration you choose.
Authentication modes
Section titled “Authentication modes”GitLab supports two models in DBModeler:
- Personal Access Token
- OAuth with PKCE
OAuth support is the richer path because the app can manage profile-oriented access and token refresh behavior directly in the browser.
Multi-profile support
Section titled “Multi-profile support”GitLab OAuth can persist more than one profile in the encrypted vault.
That means a project can be associated with:
- a default GitLab profile
- a project-specific GitLab profile
- a fallback auth method when overrides are not enabled
This is useful when different projects need to publish into different GitLab accounts or workspaces.
What the integration does
Section titled “What the integration does”Like GitHub, the active GitLab workflow is centered on migration SQL export to a repository.
You can:
- connect and validate auth
- list available repositories
- bind a project target
- choose whether to write directly or create merge-request-oriented branches
OAuth caveats
Section titled “OAuth caveats”OAuth support depends on the runtime client configuration being present.
If the GitLab OAuth client is not configured in the running build, PAT mode remains the viable option.
Recommended workflow
Section titled “Recommended workflow”Use OAuth when you want the cleanest long-lived GitLab browser flow. Use PAT when you need a simpler explicit token-based setup.
Next: Google Drive Integration