I am seriously impressed by #Forgejo's (the software powering #Codeberg and other GitHub alternatives) migration tool.

Git history, issues, PRs, wiki data; all migrated perfectly from GitHub.

You can link your GitHub account afterwards, and all migrated things move over to your user - so you can edit things like comments you originally wrote on GitHub. It's like the migration never happened.

It even migrates tiny details like comment reactions.

And because the account linking is lazy, users that haven't yet joined Codeberg aren't losing out: the moment they join and connect their account, they suddenly own everything they did on the old repository.

This is wizard shit. I'm a bit blown away at how flawless and easy the process was.

So basically I moved my spouse out of decades old #github (#grithub ?) account & decades old repos to own instance of #forgejo .
With the latest forceful nonsense of #copilot #training on your repo data does not help. Moreover, it seems #gitlab is trying to force free tier to move to paid ones. Their what's new every time makes me wonder what is going on.
Anyways, force to #selfhosting

It seems that whenever I look more closely at what #github does, it blows my mind. I had no idea that the actions/checkout which everyone seems to be using to basically run "git clone" is 38k LOC of pure node.js madness.
How about we use 9 lines of shell instead?

👋 @adyxax

https://code.vinyl-cache.org/forgejo/sane-checkout

#forgejo #forgejoActions

sane-checkout

A sane git checkout action which does not require a nodejs monster

code.vinyl-cache.org: Vinyl Cache open source code repositories

題外話, Forgejo 這名字我覺得有夠難記憶,誰取的啊 

#forgejo

@allenlinli @s8321414

有兩人推薦 Forgejo,問了一下 Gemini 似乎也是越早遷移越好,我也來準備搬家好了 (雖然才剛搬完 XD)

#gitea #forgejo

I've got a Lenovo M93p Tiny with 16GB RAM and a Haswell Xeon. It's a great little unit that I used to use as my Haiku build box.

I'm thinking about using it as a #Forgejo (and maybe eventually #Codeberg) Actions runner, with a handful of lightweight VMs (Alpine, FreeBSD, NetBSD, OpenBSD, Haiku), each using no more than a gig or two of memory.

Does anyone have any tips on doing this? I'm guessing #Proxmox would be a good start, but I wonder if #FreeBSD with #bhyve and #BastilleBSD might also do a good job.

Scaling down has a massive impact on the dev loop: Using #forgejo in dev deployments instead of #gitlab makes a cycle of teardown and bootstrap quick and snappy.

This should inform decisions about how we make software. Small and lightweight is not easy to achieve, yet it does pay back in being able to do more with the same amount of effort.

New home dashboard design and user profile screen where you will see the things which matters the most with a modern dock system.

#gitnex #app #android #codeberg #git #gitea #foss #opensource #forgejo

I have successfully migrated all my public GitHub Repos to my new Forgejo instance.
Since I don't have private repositories there, I have no GitHub Repos left.

Next step: Migrate my and my friends private repositories from my GitLab instance over to Forgejo.

#GitHub #Forgejo

I've started an overview of getting a self-hosted runner together for Codeberg here: https://fluids.rocks/posts/forgejo-self-hosted-runner/

Will follow up with at least one other post around Codeberg pages + Zola.
#selfhosted #forgejo #codeberg #zola

Setting Up Self-Hosted Forgejo Runners

Host your own CI and build workflows.