What Is GitHub to Codeberg Migration? Moving Your Repos Off GitHub

Why AI Coders Need to Know About This

Here's a question that's probably never crossed your mind: who owns the platform where all your code lives?

If you're building with AI tools — Cursor, Claude Code, Windsurf — your code almost certainly lives on GitHub. That's because when you ask AI to set up a project, the first thing it does is git init followed by instructions to push to GitHub. It's the default. It's baked into every tutorial, every template, every AI suggestion.

But GitHub is owned by Microsoft. And in recent years, a growing number of developers have started questioning what that means — especially after GitHub used public repositories to train Copilot without explicit permission from code authors. That controversy hasn't gone away. It's gotten louder.

Right now, a post about migrating from GitHub to Codeberg is trending on Hacker News with 275+ points. This isn't a fringe opinion anymore. It's a movement with real momentum, and understanding it matters even if you decide to stay on GitHub.

As a vibe coder, you need to understand your options. Your Git repositories are portable — that's the entire point of distributed version control. You're not locked in. Knowing that changes how you think about where your code lives.

What Is Codeberg?

Codeberg is a free Git hosting platform run by a non-profit organization called Codeberg e.V., registered in Berlin, Germany. Think of it as "GitHub, but run by a community instead of a corporation."

Here's what makes it different:

The interface will feel familiar if you've used GitHub. You get repositories, issues, pull requests (called "pull requests" on Codeberg too), a wiki, releases, and organizations. It's not identical — some features are simpler, some are missing — but the core workflow is the same: push code, track issues, collaborate.

Why Developers Are Leaving GitHub

This isn't about GitHub being bad. GitHub is an incredible platform that fundamentally changed how software is built. But several compounding factors have pushed developers toward alternatives:

1. The Copilot Training Controversy

In 2021, GitHub launched Copilot — an AI coding assistant trained on public GitHub repositories. The problem: many developers felt their open-source code was used without meaningful consent. Codeberg explicitly does not use your code for AI training. For developers who've spent years contributing to open source, this distinction is personal.

2. Microsoft Ownership Concerns

Microsoft acquired GitHub in 2018 for $7.5 billion. While GitHub has continued to operate semi-independently, the reality is that a trillion-dollar corporation owns the platform where most of the world's open-source code lives. Some developers see this as an unacceptable concentration of power, regardless of how benevolent the current stewardship may be.

3. Terms of Service Changes

GitHub's terms of service grant broad rights to hosted content for the purpose of operating the service. While this is standard for hosted platforms, Codeberg's non-profit structure and explicit privacy commitments offer a fundamentally different legal relationship with your code.

4. Philosophical Alignment

For many open-source developers, hosting free software on a proprietary platform owned by a mega-corporation feels contradictory. Codeberg, built on open-source Forgejo software and governed by a non-profit, aligns more closely with open-source values.

5. Centralization Risk

When one platform hosts the vast majority of the world's code, it becomes a single point of failure — technically, politically, and legally. Diversifying where code lives makes the ecosystem more resilient. This argument resonates especially with infrastructure-minded developers.

Real Scenario: Your First Migration

Let's say you've been building a side project with Claude Code. It's a simple web app — maybe 15 files, a handful of issues you've been tracking on GitHub, and a wiki page with setup instructions. You want to move it to Codeberg without losing anything.

Here's exactly what happens:

That's it. No command-line gymnastics. No exporting and importing JSON files. Codeberg's migration tool handles it because it has native GitHub integration built in. It communicates directly with GitHub's API to pull everything over.

What AI Gets Wrong About Git Hosting

When you ask AI tools about Git hosting, they overwhelmingly default to GitHub. This isn't malice — it's training data bias. Here's what AI commonly gets wrong or omits:

"Just push to GitHub"

When you ask Claude or ChatGPT to help you set up a Git repository, the instructions will almost always end with "push to GitHub." AI tools rarely mention Codeberg, Gitea, Forgejo, SourceHut, or any alternative. This is because the vast majority of tutorials, documentation, and Stack Overflow answers in their training data reference GitHub.

What to do: When you get instructions that reference GitHub, mentally replace "GitHub" with "your Git host." The Git commands themselves — git add, git commit, git push — work identically regardless of where your remote repository lives.

"Use GitHub Actions for CI/CD"

AI will frequently suggest GitHub Actions for automated testing and deployment. GitHub Actions is GitHub-specific — it won't work on Codeberg. Codeberg supports Woodpecker CI and can integrate with other CI/CD platforms.

What to do: If your AI suggests a GitHub Actions workflow, ask it to adapt the same pipeline for Woodpecker CI or a generic CI system instead.

"Store your API keys in GitHub Secrets"

AI tools often recommend GitHub Secrets for storing API keys and sensitive configuration. This is GitHub-specific. On Codeberg, you'd use Woodpecker CI secrets or environment variables in your deployment pipeline.

What to do: The principle of never committing secrets to your repository is universal. Read our guide on API key management — the concepts apply regardless of your hosting platform.

Step-by-Step: Full Migration Guide

Here's the complete process for moving a repository from GitHub to Codeberg, including updating your local development environment.

Step 1: Create Your Codeberg Account

Go to codeberg.org and register. Use the same username as your GitHub account if it's available — this makes the transition smoother for anyone who follows your work.

Step 2: Generate a GitHub Access Token

You need this so Codeberg can read your GitHub repos during migration.

# Go to: github.com/settings/tokens
# Click "Generate new token" → "Fine-grained token"
# Set these permissions:
#   - Repository access: Select the repos you want to migrate
#   - Permissions → Repository:
#     - Contents: Read-only
#     - Issues: Read-only
#     - Metadata: Read-only
# Copy the token — you'll only see it once

Step 3: Run the Migration on Codeberg

On Codeberg, click the + button in the top-right corner, then select New Migration. Select GitHub as your source platform.

Fill in:

• Clone URL: The full URL of your GitHub repo (e.g., https://github.com/yourname/my-project)
• Access Token: Paste the token you generated in Step 2
• Repository Name: Keep it the same as on GitHub for consistency
• Visibility: Public or Private — your choice
• Migration Items: Check everything you want to bring over — issues, labels, milestones, releases, wiki

Click Migrate Repository. For a typical project, this takes 30 seconds to a few minutes depending on size.

Step 4: Update Your Local Git Remote

After migration, your local copy still points to GitHub. You need to update it to point to Codeberg:

# See your current remote (it will say github.com)
git remote -v

# Option A: Replace GitHub with Codeberg entirely
git remote set-url origin https://codeberg.org/yourname/my-project.git

# Option B: Keep both (push to Codeberg, keep GitHub as a mirror)
git remote set-url origin https://codeberg.org/yourname/my-project.git
git remote set-url --push --add origin https://github.com/yourname/my-project.git
git remote set-url --push --add origin https://codeberg.org/yourname/my-project.git

# Verify the change
git remote -v
# origin  https://codeberg.org/yourname/my-project.git (fetch)
# origin  https://codeberg.org/yourname/my-project.git (push)

Step 5: Set Up SSH Keys for Codeberg

If you use SSH for Git (and you should), you'll need to add your SSH key to Codeberg:

# Check if you already have an SSH key
ls ~/.ssh/id_ed25519.pub

# If not, generate one
ssh-keygen -t ed25519 -C "your-email@example.com"

# Copy your public key
cat ~/.ssh/id_ed25519.pub
# Copy the output

Go to Codeberg → Settings → SSH/GPG Keys → Add Key. Paste your public key. Now you can use SSH URLs:

# Switch your remote to SSH
git remote set-url origin git@codeberg.org:yourname/my-project.git

# Test the connection
ssh -T git@codeberg.org
# Hi yourname! You've successfully authenticated.

Step 6: Archive Your GitHub Repo (Optional)

If you want to signal that development has moved to Codeberg:

• Go to your GitHub repo → Settings → scroll to "Danger Zone"
• Click "Archive this repository"
• Update the repo description to: "⚠️ Moved to codeberg.org/yourname/my-project"
• Add a note to the README pointing to the new location

What Changes for Your AI Workflow

This is the section that matters most for vibe coders. When you move from GitHub to Codeberg, what actually changes in your day-to-day AI-assisted development?

✅ What Stays the Same

• All Git commands: git add, git commit, git push, git pull, git branch — everything works identically. Git is Git, regardless of the remote host.
• Claude Code / Cursor / Windsurf: These tools work with local Git repos. They don't care where the remote is. Your AI coding experience is unchanged.
• VS Code integration: The built-in Git support in VS Code works with any Git remote. Codeberg repos work out of the box.
• Terminal workflows: If you work in the terminal, absolutely nothing changes in how you interact with your code.
• Branching, merging, PRs: Codeberg supports pull requests with the same review workflow as GitHub.

⚠️ What Changes

• GitHub Actions → Woodpecker CI: This is the biggest change. GitHub Actions workflows don't transfer. You'll need to set up CI/CD using Woodpecker CI or an external service. The concepts are the same, but the configuration format is different.
• GitHub Copilot: If you use Copilot, it's GitHub-specific. On Codeberg, you'd use alternatives like Claude Code, Cursor, or Windsurf — which work with any Git host and are likely what you're already using as a vibe coder.
• GitHub Pages: For static site hosting, Codeberg offers Codeberg Pages — push to a pages branch and your site is live at yourname.codeberg.page.
• AI default suggestions: When you ask AI to set up deployment or CI, it will default to GitHub. You'll need to specify: "I use Codeberg, not GitHub. Suggest Codeberg-compatible alternatives."
• Package registries: GitHub Packages (npm, Docker, etc.) won't be available. Codeberg has a built-in package registry for common formats, or you use external registries.
• Community size: GitHub has 100M+ users. Codeberg has ~300K. Your open-source project may get less visibility on Codeberg — though many developers maintain a GitHub mirror for discoverability.

My code is hosted on Codeberg (codeberg.org), not GitHub.
When suggesting CI/CD, use Woodpecker CI instead of GitHub Actions.
When suggesting hosting, use Codeberg Pages instead of GitHub Pages.
When suggesting remote URLs, use codeberg.org instead of github.com.
Do not suggest GitHub-specific features like GitHub Copilot or GitHub Secrets.

Mirroring: The Best of Both Worlds

You don't have to choose one platform exclusively. Many developers use Codeberg as their primary host while maintaining a read-only mirror on GitHub for visibility. Here's how to set that up:

# Set up dual push (pushes to both on every git push)
git remote set-url --push --add origin git@codeberg.org:yourname/my-project.git
git remote set-url --push --add origin git@github.com:yourname/my-project.git

# Now when you push:
git push origin main
# → Pushes to codeberg.org AND github.com simultaneously

# Verify your setup
git remote -v
# origin  git@codeberg.org:yourname/my-project.git (fetch)
# origin  git@codeberg.org:yourname/my-project.git (push)
# origin  git@github.com:yourname/my-project.git (push)

This way, your Codeberg repo is the source of truth, but anyone searching GitHub can still find your project and get directed to where active development happens.

When to Stay on GitHub

Honest assessment: migrating isn't right for everyone. Here are legitimate reasons to stay on GitHub:

• Your team uses GitHub extensively: If you collaborate with people deeply invested in the GitHub ecosystem (Actions, Projects, Discussions), switching has a real coordination cost.
• You depend on GitHub-specific integrations: Vercel, Netlify, Railway, and many deployment platforms have first-class GitHub integration. Codeberg support varies.
• Open-source discoverability matters: If you're trying to grow an open-source project, GitHub's 100M+ user base provides significantly more exposure than Codeberg's 300K.
• You use GitHub Copilot heavily: Copilot is tied to GitHub. If it's central to your workflow, migrating means replacing it — though tools like OpenRouter give you access to multiple AI models that serve similar purposes.

There's no shame in staying on GitHub while acknowledging the tradeoffs. The point is to make an informed choice rather than accepting the default because it's what AI always suggests.

What to Learn Next

Frequently Asked Questions