GitHub Integration

Use the GitHub integration to push migration SQL from DBModeler into a repository you control.

Authentication model

GitHub currently uses a Personal Access Token workflow.

DBModeler tests the token against the GitHub API and can cache it in memory. When the secret manager is enabled and unlocked, token persistence can be protected through the encrypted vault instead of plain browser state.

What GitHub integration does today

The active workflow is focused on migrations.

connect a PAT
fetch accessible repositories
bind a project to a repository target
choose a branch strategy
push version SQL after creating a version

Repository and branch strategy

Project configuration separates where migrations should be written from how they should be committed.

Typical branch strategies are:

commit directly to the default branch
create a version-specific branch and open a pull request workflow

This makes GitHub integration useful both for solo flows and for review-based team workflows.

What gets pushed

The integration is designed around generated migration SQL for versions.

Schema export targets may exist in the configuration model, but the active path today is migrations-first.

Common limits

GitHub integration is PAT-based, not OAuth-based.
Repository listing is paginated and intentionally capped.
The workflow is for repository output, not for editing the DBModeler project directly inside GitHub.

Recommended workflow

create and review a version in DBModeler
preview the migration SQL locally
push through GitHub with the branch strategy you want
review the resulting PR or commit in the repository

Next: GitLab Integration