Importing Repositories
GitBlixt can import your existing repositories from GitHub, GitLab.com, or a self-hosted GitLab instance. The import process copies your repository's code, branches, tags, issues, merge/pull requests, and comments into GitBlixt.
What Gets Imported
| Entity | GitHub | GitLab |
|---|---|---|
| Git history (all branches & tags) | Yes | Yes |
| Issues | Yes | Yes |
| Pull Requests / Merge Requests | Yes | Yes |
| Comments & review threads | Yes | Yes |
| Labels | Yes | Yes |
| Milestones | Yes | Yes |
| Wikis | Yes | Yes |
| Repository metadata (description, visibility) | Yes | Yes |
Not imported: CI/CD pipeline history, GitHub Actions workflows, GitLab CI artifacts, deploy keys, webhooks. These must be reconfigured manually after import.
GitHub issues, pull requests and comments keep their original dates. Their author is the GitBlixt user with the same username; without one, the importing user becomes the author and the text starts with Created by: github-username. A Fetch from remote by a user with a connected GitHub account adds the dates and that line to items imported before; an item keeps the author it was first imported with.
Import Methods
UI Import (recommended for most users) — connect your GitHub or GitLab account, browse your repositories, select the ones you want, and click Import. Available from your dashboard.
CLI Import (for administrators doing bulk migrations)
— a mix
task that can import an entire GitHub organization or GitLab group at once. See the relevant
import guide for details.
How Long Does It Take?
A typical repository with a few hundred issues imports in under a minute. Repositories with thousands of issues and PR comments may take several minutes. Progress is shown in real time.