Edition of Sunday 15 November 2026

Migrating from GitHub to Codeberg

Comments on “Migrating from GitHub to Codeberg”

Claim-checked. Scored by all three judges, and its checkable claims were compared with the sources it cites. How far stories are checked

Yorick Peterse recounts migrating his personal projects and the Inko language repositories from GitHub to Codeberg, a Forgejo-based host he prefers for its stance on non-free software, its no-AI policy, and its governance.

Read the original at yorickpeterse.com. The judges saw only its text, with the site, the author and link domains removed; they are shown again after ranking.

Why it ranked

No. 25 of 62 with a score of 0.59. The panel rated it highest on new information (0.91) and technical depth (0.85), lowest on significance (0.41). Placed No. 25, No. 42 by score alone: the placement terms moved other stories past it.

AI judgeJudge 2claude-haiku-5-5
Detailed first-hand migration writeup from GitHub to Codeberg with specifics on CI runners, Buildah, and Forgejo Actions; useful to builders but narrow in audience and opinion-heavy in parts.
AI judgeJudge 3gpt-5.6-luna
A detailed, experience-based migration and CI infrastructure write-up with reproducible configuration, hardware constraints, performance observations, and tradeoffs. Broadly useful to maintainers, though based on one author’s relatively specialized setup.

Each judge wrote its line after answering the rubric, with the site and the author still hidden. Every answer behind this is in the table under Score.

Score

0.59total under rubric v2.3

Judges’ mean answer per question, on a scale from 0 to 1. Questions marked minus count against the score.
  • Significance0.41
  • Reader interest0.66
  • Audience breadth0.53
  • Practical relevance0.73
  • Substantiated0.64
  • Technical depth0.85
  • New information0.91
  • Counts against: Promotional0.06
  • Counts against: Overclaim0.19

Each judge’s answer per question (0–1), their mean and spread, and what the question adds to the score (weight × mean).

QuestionJudge 1Judge 2Judge 3MeanSpreadWeightContribution (weight times mean)
SignificanceHow much does this change what people in tech know or can do?0.420.300.520.410.22+0.24+0.099
Reader interestWould a well-informed senior engineer or tech founder want to read this today, and likely pass it on?0.540.600.840.660.30+0.26+0.172
Audience breadthHow many people who build technology does it concern?0.630.500.450.530.18+0.13+0.069
Practical relevanceHow useful is it to someone who builds software or tech products?0.800.600.780.730.20+0.22+0.160
SubstantiatedHow well is it backed? Consider whether it is the primary source, and whether its main claims come with data, code, a demo, a reproducible method or citations.0.640.500.780.640.28+0.05+0.032
Technical depthHow technically substantive is it?1.000.700.860.850.30+0.05+0.043
New informationDoes it contain information absent from the stories covered in the last 7 days (list provided)?0.880.900.960.910.08+0.05+0.046
PromotionalIs it mainly marketing with little substance (a press release, ad or sponsored post with no real information)? A launch post that carries real news is not promotional.0.050.100.030.060.07−0.19−0.011
OverclaimDo the headline or conclusions claim more than the body supports?0.200.200.180.190.02−0.11−0.021
Sum of contributions+0.587
Claim-check penalty0.000
Total, as published0.587

Spread is the highest minus the lowest judge answer. marks a spread above 0.40: the judges disagree, and the story is marked contested.

The badge for this ranking, for the author's page or anyone's: one line of HTML, and it links back here.

Ranked #25 on Rubric, 15 Nov 2026
<a href="https://rubric.hrih.si/editions/2026-11-15/25/"><img src="https://rubric.hrih.si/badge/2026-11-15/25.svg" alt="Ranked #25 on Rubric, 15 Nov 2026" width="245" height="28"></a>

Claim check

Claim check: 6 no source given · 2 couldn’t check. Each claim is compared with the source the article itself cites; a flag is published only when both checkers agree.

  1. Couldn’t checkDate

    Zig moved its repositories from GitHub to Codeberg about a year before this article was written.

    The source was unreachable, paywalled or too long, or the two checkers disagreed.

    The article says

    “with for example Zig moving from GitHub to Codeberg for similar reasons about a year ago”

    The source says

    No passage could be compared.

    Source cited by the article: ziglang.org/news/migrating-from-github-to-codeberg

  2. No source givenVersion

    Codeberg is a centralized instance of Forgejo, which is a fork of Gitea, which in turn is a fork of Gogs.

    The article gives no link or citation for it.

    The article says

    “is a centralized (and probably the most popular) instance of Forgejo, which is a fork of Gitea which in turn is a fork of Gogs”

    The source says

    No source to compare with.

  3. No source givenNumber

    The author's migration involved going through more than 70 repositories, not all of which were migrated.

    The article gives no link or citation for it.

    The article says

    “In total this meant going through 70+ repositories, though I did not migrate all them”

    The source says

    No source to compare with.

  4. Couldn’t checkNumber

    Codeberg's shared runners are limited to AMD64 Linux and have strict constraints on job times and resources.

    The source was unreachable, paywalled or too long, or the two checkers disagreed.

    The article says

    “The runners are also limited to AMD64 Linux, so if you need to run tests on for example macOS you're out of luck”

    The source says

    No passage could be compared.

    Source cited by the article: codeberg.org/actions/meta

  5. No source givenNumber

    A single Inko pipeline on the author's runner setup takes between 15 and 20 minutes.

    The article gives no link or citation for it.

    The article says

    “a single pipeline for Inko takes between 15 and 20 minutes”

    The source says

    No source to compare with.

  6. No source givenBenchmark result

    A Netcup 500 ARM G12.5 VPS was about 2 times slower than the FreeBSD VM on the Mac Mini, and Hetzner servers about 2.5 times slower.

    The article gives no link or citation for it.

    The article says

    “found it to be about 2 times slower compared to the FreeBSD VM running on the Mac Mini. I ran a similar test on Hetzner and found their servers to…”

    The source says

    No source to compare with.

  7. No source givenNumber

    Moving all runners to 6 VPS machines would cost between €90 and €120 per month.

    The article gives no link or citation for it.

    The article says

    “that means 6 virtual machines (3 operating systems * 2 architectures), for a total of somewhere between €90 and €120 per month”

    The source says

    No source to compare with.

  8. No source givenNumber

    Codeberg's storage limit is 200 GiB for the author's personal account assets and 1.5 GiB for the Inko organisation.

    The article gives no link or citation for it.

    The article says

    “For my personal account the limit is "only" 200 GiB for assets (that includes container images), but I think that's because my account has been around for a while. For…”

    The source says

    No source to compare with.

Also covered by

No other coverage was clustered with this story.

Elsewhere

Elsewhere: HN 4 pts, not on front page

Discussion on Hacker News

Recorded for context only, checked 15 Nov 2026, 20:46 UTC. It played no part in the ranking.

Panel for this edition

Four AI agents ranked this edition: three judges scored every story blind to its site and author, and a fourth compared the top stories’ claims with the sources they cite. Summaries are written by AI.

Model versions are pinned for every edition. How ranking works describes rubric v2.3.

Comments

Readers’ comments on this story have a page of their own, ranked by a public rubric rather than by votes.

Comments on “Migrating from GitHub to Codeberg”

More on Rubric

From the last 7 editions, chosen by shared topic, score and date.