Getting StartedMigration

Migrate from GitHub

Import repositories from GitHub with full history, branches, tags, issues, and merge requests.

Drok provides a one-command migration path from GitHub. The import process preserves the complete repository history — every commit, every branch, every tag — and optionally migrates issues, pull requests (converted to merge requests), labels, milestones, and wiki content.

Quick Migration

Import a single repository:

drok import github your-org/your-repo

This clones the repository with full history and pushes it to your Drok account at drok.us/your-username/your-repo.

Organization Migration

Import an entire GitHub organization:

drok import github --org your-org --all

This imports every repository in the organization, preserving the org structure. Requires a GitHub personal access token with repo and read:org scopes.

What Gets Migrated

ComponentMigratedNotes
Git historyYesComplete — every commit, branch, tag
IssuesYesWith comments, labels, assignees, milestones
Pull requestsYesConverted to merge requests with review comments
LabelsYesColors and descriptions preserved
MilestonesYesWith due dates and descriptions
WikiYesConverted to repository wiki
ReleasesYesWith assets and release notes
Branch protectionYesConverted to Drok branch protection rules
CODEOWNERSYesSyntax is identical
Actions workflowsPartialConverted to .lehub/pipeline.yml where possible

Authentication for Import

The import tool requires a GitHub personal access token:

drok import github your-org/your-repo --github-token ghp_xxxxxxxxxxxx

Or set it as an environment variable:

export GITHUB_TOKEN=ghp_xxxxxxxxxxxx
drok import github your-org/your-repo

The token is used only for the import operation and is not stored.

Post-Migration

After importing:

  1. Update your remotes — Switch local clones to point to Drok:

    git remote set-url origin https://drok.us/your-username/your-repo.git
  2. Configure Pipelines — Convert GitHub Actions workflows to Drok Pipelines. See Pipelines.

  3. Update CI/CD badges — Replace GitHub status badges with Drok pipeline badges.

  4. Invite collaborators — Set up your organization and team structure. See Teams.

Parallel Operation

You do not need to migrate all at once. Drok and GitHub can operate in parallel during your transition. Push to both remotes, run CI on both platforms, and migrate teams incrementally as confidence builds.

git remote add drok https://drok.us/your-username/your-repo.git
git push drok main
git push origin main