Linux

48031 readers

770 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
No misinformation
No NSFW content
No hate speech, bigotry, etc

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 5 years ago

MODERATORS

nooter692@lemmy.ml

AgreeableLandscape@lemmy.ml

MarcellusDrum@lemmy.ml

cypherpunks@lemmy.ml

cyclohexane@lemmy.ml

d3Xt3r@lemmy.nz

Automated Archival-Level Git Repo Mirroring? (leminal.space)

submitted 7 months ago by fenndev@leminal.space to c/linux@lemmy.ml

11 comments fedilink hide all child comments

cross-posted from: https://leminal.space/post/4761745

Shortly before the recent removal of Yuzu and Citra from Github, attempts were made to back up and archive both Github repos; it's my understanding that these backups, forks, etc. are fairly incomplete, either lacking full Git history or lacking Pull Requests, issues, discussions, etc.

I'm wondering if folks here have information on how to perform thorough backups of public, hosted git repos (e.g. Github, Gitlab, Codeberg, etc.). I'd also like to automate this process if I can.

git clone --mirror is something I've looked into for a baseline, with backup-github-repo looking like a decent place to start for what isn't covered by git clone.

The issues I can foresee:

Each platform builds its own tooling atop Git, like Issues and Pull Requests from Github

Automating this process might be tricky

Not having direct access/contributor permissions for the Git repos might complicate things, not sure

I'd appreciate any help you could provide.

you are viewing a single comment's thread
view the rest of the comments

[–] mesamunefire@lemmy.world 4 points 7 months ago

Gitlab has really good automated tools for the initial pull from GH to GL. I remember coming across some GitHub actions and ci/cd tools that auto push changes from one fork to another. The biggest issue is the bundled binaries. I dont remember seeing any automated tools for that.