Docs: a migration guide for repositories coming from GitHub or GitLab #182

Nytt ärende

supernaut · 2026-08-02T21:09:09Z

supernaut kommenterad

2026-08-02 21:09:09 +00:00

Ägare

Nothing on the site tells a visitor how to move an existing repository onto Bitborg, or what comes
across when they do. It is the first question anyone already settled on another host asks, and
answering it in prose removes a real switching cost.

Not a launch blocker, unlike the getting-started guide in gitborg/gitborg-web#181. Sequence it
behind that one.

Scope

One guide covering both origins rather than two near-identical ones — the import path and most of
the content are shared, and a single page is also the one a search lands on:

src/content/guides/sv/migrating-from-github-or-gitlab.md
src/content/guides/en/migrating-from-github-or-gitlab.md

Covering:

how to run the import
what actually transfers and what does not — repository history, issues, pull requests,
releases, wiki, labels, milestones: each one verified rather than assumed
continuous integration after the move: what has to change in a workflow coming from GitHub Actions
or GitLab CI, since the workflow file does not carry over unchanged
a one-off import versus an ongoing mirror, and when each is the right choice
the sovereignty point, stated plainly: once the repository is here it is on Swedish
infrastructure, under Swedish and EU jurisdiction

The honest half matters more than the reassuring half. A migration guide that omits what is lost is
worse than none, because the loss is then discovered after the switch.

Wiring

Same shape as gitborg/gitborg-web#181:

guides collection, both locales, frontmatter per the schema in src/content.config.ts
a topic slug registered in src/i18n/topics.ts — suggested migration →
{ en: "Migration", sv: "Migrering" }
order placing it after the getting-started guide

The original plan linked this guide from a comparison page. That page is out of scope for the epic
(see gitborg/gitborg-docs#28), so link it from /docs and from the getting-started guide's closing
"where to go next" instead.

Definition of done

every claim about what transfers is checked against a real import into a scratch repository, and
the guide names what does not come across
appears on both /docs and /en/docs in the intended position
pnpm build passes (frontmatter is build-enforced and feeds the sitemap)
Swedish copy uses Forgejo's sv-SE terms with an English gloss on first use
pnpm lang-check passes
sv/en parity

Part of gitborg/gitborg-docs#28.

Nothing on the site tells a visitor how to move an existing repository onto Bitborg, or what comes across when they do. It is the first question anyone already settled on another host asks, and answering it in prose removes a real switching cost. Not a launch blocker, unlike the getting-started guide in gitborg/gitborg-web#181. Sequence it behind that one. ## Scope One guide covering both origins rather than two near-identical ones — the import path and most of the content are shared, and a single page is also the one a search lands on: - `src/content/guides/sv/migrating-from-github-or-gitlab.md` - `src/content/guides/en/migrating-from-github-or-gitlab.md` Covering: - how to run the import - **what actually transfers and what does not** — repository history, issues, pull requests, releases, wiki, labels, milestones: each one verified rather than assumed - continuous integration after the move: what has to change in a workflow coming from GitHub Actions or GitLab CI, since the workflow file does not carry over unchanged - a one-off import versus an ongoing mirror, and when each is the right choice - the sovereignty point, stated plainly: once the repository is here it is on Swedish infrastructure, under Swedish and EU jurisdiction The honest half matters more than the reassuring half. A migration guide that omits what is lost is worse than none, because the loss is then discovered after the switch. ## Wiring Same shape as gitborg/gitborg-web#181: - `guides` collection, both locales, frontmatter per the schema in `src/content.config.ts` - a `topic` slug registered in `src/i18n/topics.ts` — suggested `migration` → `{ en: "Migration", sv: "Migrering" }` - `order` placing it after the getting-started guide The original plan linked this guide from a comparison page. That page is out of scope for the epic (see gitborg/gitborg-docs#28), so link it from `/docs` and from the getting-started guide's closing "where to go next" instead. ## Definition of done - every claim about what transfers is checked against a real import into a scratch repository, and the guide names what does not come across - appears on both `/docs` and `/en/docs` in the intended position - `pnpm build` passes (frontmatter is build-enforced and feeds the sitemap) - Swedish copy uses Forgejo's `sv-SE` terms with an English gloss on first use - `pnpm lang-check` passes - sv/en parity Part of gitborg/gitborg-docs#28.

supernaut lade till etiketterna

area/web

ready-for-implementation

type

docs

2026-08-02 21:09:24 +00:00

supernaut refererade till detta ärende

2026-08-02 21:09:52 +00:00

Docs: a getting-started guide, from account to first push #181

~~supernaut refererade till detta ärende från bitborg/bitborg-docs 2026-08-02 21:11:19 +00:00~~

Public site conversion & trust surface #28

supernaut lade till detta till projektet Bitborg Web