Zum Hauptinhalt springen
Echtzeit-Radar & Feeds
Alle RSS Feeds ➔
👥 Community & Social
Windows Tipps & SecurityGrafikkarte vor Überhitzung schützen: So geht’s(25.09.2026 um 08:00 Uhr)
••••••••••
Windows Tipps & SecurityGrafikkarte vor Überhitzung schützen: So geht’s(25.09.2026 um 08:00 Uhr)
••••••••••
Intelligence View
⚡ tsecurity.de Intelligence

Moving from GitHub to Codeberg(Forgejo)

NOTE: This post is written from a private developer perspective, not that of my employer. I've started migrating my active projects from GitHub to Codeberg. Codeberg is a European open-source alternative that overall resembles GitHub—a c…

0
↗ Quelle (dev.to)
Reagiere als Erste:r — dein Feedback zählt!

NOTE: This post is written from a private developer perspective, not that of my employer.



I've started migrating my active projects from GitHub to Codeberg.

Codeberg is a European open-source alternative that overall resembles GitHub—a code collaboration platform.

I'd been considering it for a while, and now that it's almost done, I wanted to share my thoughts.j



Why?



One thing I've increasingly felt about GitHub is that they ignore basic, important developer features while prioritizing other unrequested ones.

What I miss includes fast-forward merges for linear history, rebase-only repos, SHA256 support, and AsciiDoc rendering that's still missing or broken.

The whole markup rendering is a mess with uneven support for different formats.

Full token security has been requested for a long time, yet we still have to use old, insecure Classic tokens for publishing packages (fine-grained tokens aren't done).

Many solutions end up 80% done and then seem to stall.

Maybe it's telling that the open source parts, like the GitHub markup repo, seem abandoned.

There are issues sitting for years, and the commit history shows no steady stewardship.

Overall it feels like GitHub has, in some areas, stopped prioritizing developer community needs and technical excellence.

Much of GitHub is historically good too, of course, but I expect far more technical drive and listening to the developer community from such a widely used global service.



But not only that—lately I've also been thinking more about how important digital sovereignty is; no surprise, given the crises around us.

GitHub is under US law, which has unfortunately become a liability.

The idea of developers being cut off from their projects because of "tweet-of-the-day-and-it's-consequences"-politics is no longer far-fetched.

Developers have historically been banned from the platform in regards to US sanctions.

My, and many other developers', trust in US data services was already damaged by the stories of FISA702 and the NSA way back, and it hasn't grown stronger in recent years, in particular the two latest ones.

Against that backdrop, supporting an initiative in Europe, under EU law, feels both motivated and straightforward.



So, if not GitHub, what then?

I looked around.

GitLab?

I also like GitLab a lot and have used it for years at work and privately.

It's partly open source, which is better than GitHub's total black box.

But I wanted something European, more community-driven—something where I could fix a feature myself if the platform didn't.

Sourcehut?

No—too bare-bones.



The choice fell on Codeberg.

Codeberg is run by a non-profit foundation that runs on the open-source project Forgejo.

You can self-host components like runners, you can contribute solutions and future directions, and the foundation is EU-based.

It's not just another "GitHub" clone.

For example, they're working on adding federation support.

Forgejo is written in Go, and it shows—the platform feels snappy and fast.



I started moving my projects over.

Transferring code, features like Pages, and Renovate was fairly easy.

Setting up more advanced CI flows required extra work, partly because there are still unresolved issues.

You also have to set up your own runners (I used Podman-based ones).

While Forgejo Actions are similar to GitHub Actions, there are some differences in how they work.

So expect to miss features you're used to having from GitHub Actions and maybe GitLab CI.



Sure, the goal is probably not for Codeberg to reach feature parity with GitHub and others, but as an end user every such feature helps me migrate.

So personally I hope they get even closer to parity.

That doesn't rule out solving the same user needs in even better ways.



I will still work on GitHub, and will keep contributing to projects there, both for myself and for my job.

My point is simply that it’s worth thinking about who owns FOSS infrastructure and who controls it sometimes.

If there are equivalent alternatives, maybe choose them instead.



Conclusion:



If you're a tech-minded individual with accounts or projects already on GitHub, GitLab, etc, I'd definitely say—give Codeberg a shot for your projects.

Set up a Runner and get started.

If you're an organization, I'd suggest waiting until some of the missing features are resolved (or maybe better, start to fix them).



PS Here's a post about the rough edges I hit during the migration:





Relevant References



1. Sofort-Triage & Abwehrmaßnahmen

SOC Incident Playbook: Remote Code Execution (RCE) Defense
Syntax validiert (0 Fehler)
title: Detect Exploitation - Moving from GitHub to Codeberg(Forgejo)
id: 6ac482c8-0d3b-4c38-ad80-86d25785fc5b
status: experimental
description: Automatisch generierte SIEM-Erkennungsregel basierend auf CTI Intelligence
references:
  - https://tsecurity.de/
author: iShareStuff CTI Automated Detection Engine
date: 2026-09-26
logsource:
  category: network_connection
  product: any
detection:
  selection:
      CommandLine|contains:
        - 'exploit'
  condition: selection
falsepositives:
  - Legitime administrative Zugriffe oder Penetrationstests
level: high
tags:
  - attack.initial_access
Syntax validiert (0 Fehler)
rule CTI_Threat_Indicator {
    meta:
        author = "iShareStuff CTI Automated Detection Engine"
        date = "2026-09-26"
        description = "YARA Signature for "
    strings:
        $str = "Moving from GitHub to Codeberg" ascii wide
    condition:
        any of them
}
Syntax validiert (0 Fehler)
index=security sourcetype IN ("cisco:asa", "pan:traffic", "zeek_conn", "suricata", "WinEventLog:Security")
("Moving from GitHub to CodebergForgejo")
| stats count earliest(_time) as first_seen latest(_time) as last_seen by src_ip, dest_ip, dest_host, signature
| eval first_seen=strftime(first_seen, "%Y-%m-%d %H:%M:%S"), last_seen=strftime(last_seen, "%Y-%m-%d %H:%M:%S")
| sort - count
Syntax validiert (0 Fehler)
message: "*Moving from GitHub to CodebergForgejo*"
Syntax validiert (0 Fehler)
CommonSecurityLog
| where Message has "Moving from GitHub to CodebergForgejo"
| summarize EventCount = count(), FirstSeen = min(TimeGenerated), LastSeen = max(TimeGenerated) by SourceIP, DestinationIP, DestinationPort, Activity
| extend DetectionRule = "iShareStuff-CTI-Compiled"
| sort by EventCount desc

2. Cyber Threat Intelligence & Forensik

CTI Threat Relationship Graph2 Knoten / 1 Relationen
CVE / Incident Software MITRE ATT&CK CWE Weakness IoC
🎯
MITRE ATT&CK Matrix Navigator 14 Taktiken
Reconnaissance
-
Resource Development
-
Initial Access
Execution
Persistence
-
Privilege Escalation
Defense Evasion
Credential Access
-
Discovery
-
Lateral Movement
-
Collection
-
Command and Control
Exfiltration
-
Impact
tsecurity.de Cognitive Threat RAG
Fokus-Vektor:

Kognitive Analyse für identifizierte Bedrohung: Erhöhte Bedrohungslage im Bereich Moving from GitHub to Codeberg(Forgejo).... Basierend auf 368k Vektor-Korrelationen werden sofortige Isolationsmaßnahmen für betroffene Endpunkte empfohlen.

🛡️ Angriffsfläche & Exposure

Netzwerk/Remote-Zugriff ohne Vorauthentifizierung möglich.

⚡ Empfohlene Sofortmaßnahmen
  • 1. Perimeter-Inspektion: Relevante Portfreigaben und exponierte Endpunkte unverzüglich scannen.
  • 2. Patch-Applikation: Hersteller-Hotfix einspielen oder betroffene Daemons in isolierte DMZ-Segmente überführen.
  • 3. Telemetrie & EDR-Alerts: Prozessaufrufe und Child-Processes auf anomale Shell-Spawns überwachen.
🔗 Semantisch verwandte Zero-Days MariaDB 11.7 VEC
Ähnliche Beiträge
🔍 Verwandte News

Auch interessante Nachrichten Moving from GitHub to Codeberg(Forgejo)

Thematisch verwandte Begriffe: Moving, from, GitHub, CodebergForgejo · 6 Treffer

Laden...

Videos werden geladen ...

Laden...

Beiträge werden geladen ...

Laden...

Videos werden geladen ...

Laden...

Beiträge werden geladen ...

Laden...

Videos werden geladen ...

Laden...

Beiträge werden geladen ...

Laden...

Videos werden geladen ...

Laden...

Beiträge werden geladen ...

Laden...

Videos werden geladen ...

Zum Aktualisieren ziehen
ZERO-DAY CVE-2026-100534 | OpenClaw versions before 2026.8.1 contain an authorization bypass vulne…
Advisory →
tsecurity.de Icon
Offline-Lesen, Eilmeldungen & 0ms Ladezeit

Installiere tsecurity.de direkt auf deinen Home-Bildschirm für das ultimative Vollbild-Magazinerlebnis ohne Browser-Leisten.

Nächster Beitrag