GitHub is "The AI-powered developer platform".

Not the "Build software better, together. Powerful collaboration, code review, and code management for open source and private projects." we signed up for years ago. (github's main page from webarchive).

@fedor I'm so glad that I'm migrating to codeberg (for FOSS) and sourcehut (anything else).
@Andre_LA @fedor Why not FOSS on SourceHut?

@mcepl
@fedor

The last time I saw, codeberg seems easier for contribution.

Short GitHub patch workflow demo

PeerTube

@mcepl

Sadly I can't read this link on my browser (it returns a json), but I suppose it's the e-mail workflow?

https://drewdevault.com/2018/07/02/Email-driven-git.html

In case it is:

Easier doesn't necessarily means better, I also like Drew's method, and I plan to learn it well eventually, but I appreciate codeberg's low entry barrier.

Also, I'm a game developer, and sometimes I share with artists (or any non-programmers) links to the repository, so an not-so-technical navigation helps them.

The advantages of an email-driven git workflow

@mcepl @Andre_LA correct comparison would be with this process: https://spacepub.space/w/9Dfeq3fBXABUQPY8XR4RgU

I for sure can see how github-like workflow could be considered easier.

Live stream archive: reviewing patches by email

PeerTube

@fedor @mcepl

Got the first video working, just watched now, pretty nice, I did a check, and fortunately codeberg doesn't hides the .patch (although not that visible either).

On a pull request, you go on the changed files, and on the options dropdown there's the button to download the patch.

Or just add ".patch" at the end of the URL of the PR.

Anyway, I appreciate codeberg's way, even GH-like can be hard to learn for who is just starting, but it doesn't hides the patch file as GH does.