News for hackers. Stuff that matters.
Re:Incident with Github.com by jeremyjh on Monday August 17, 2026 @10:12AM (#49331304)
Yes but on Earth every project needs a canonical main branch. Most also need a way to manage and review changes to that branch that all project members have direct access to.
Re:Incident with Github.com by Sanzig on Monday August 17, 2026 @10:19AM (#49331429)
Gitea (and its popular fork, Forgejo) are very lightweight. You can easily stand up an instance on a cheap VPS.
Re:Incident with Github.com by jeremyjh on Monday August 17, 2026 @03:27PM (#49336343)
Agreed. Just moved some of my projects to codefloe.com (Forgejo) this weekend. FYI - it provides a lot more than a link to git.
Re:Incident with Github.com by skydhash on Monday August 17, 2026 @10:23AM (#49331499)
It's on the project to decide which is canonical and export a read only accessible version. Change review only requires a communication medium (the patches are mostly plain text) and that can be done in a lot of way. As for merging those changes, it's an organizational issue.
Re:Incident with Github.com by jeremyjh on Monday August 17, 2026 @03:25PM (#49336306)
If it’s on the project to determine their requirements, why are you doing it?