Skip to content

fix(amber): balance the why paragraph against the wip status #11

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
TitusKirch merged 1 commit into from
Aug 6, 2026
Merged

fix(amber): balance the why paragraph against the wip status #11

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion projects/TitusKirch/amber/de.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,7 @@ Soll Git-Repositories samt ihrer Forge-Metadaten sichern: Issues, Pull Requests,

Ein git clone rettet den Code. Alles andere verschwindet, sobald ein Konto gesperrt oder eine Organisation gelöscht wird: die Diskussion in den Issues, die Kommentare an den Pull Requests, die Releases samt Notizen, die Labels und Meilensteine.

Diesen Teil soll amber mitsichern. Vorgesehen ist ein vollständiger git-Spiegel mit allen Branches und Tags, daneben die Metadaten als JSON, dazu ein Manifest mit Integritäts-Hashes und inkrementelle Läufe, die beim zweiten Durchgang nur noch Geändertes holen. Abgelegt wird in gewöhnlichen Ordnern, die auch ohne amber lesbar bleiben.
Diesen Teil soll amber mitsichern, neben dem git-Spiegel selbst.

## scope

Expand Down
2 changes: 1 addition & 1 deletion projects/TitusKirch/amber/en.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,7 @@ Aims to back up Git repositories along with their forge metadata: issues, pull r

A git clone saves the code. Everything else disappears the moment an account is suspended or an organisation deleted: the discussion in the issues, the comments on the pull requests, the releases and their notes, the labels and milestones.

That is the part amber is meant to capture. The plan is a full git mirror with every branch and tag, the metadata as JSON beside it, a manifest with integrity hashes, and incremental runs that fetch only what changed on the second pass. Storage is ordinary folders that stay readable without amber.
That is the part amber is meant to capture, alongside the git mirror itself.

## scope

Expand Down