[flagged]
Moving from GitHub to Codeberg, for lazy people
311–320 of 385 posts
Re: Moving from GitHub to Codeberg, for lazy people
#312Earlier quoted context omitted.
Exactly. Any github alternative needs to consume same GithubActions syntax OOTB I'm afraid.
Which, as far as I found so far, means Forgejo. Haven't found any others. And even Forgejo Actions says that it's mostly the same as Github Actions syntax, meaning you still have to double-check that everything still works the same. It probably will, but if you don't know what the corner cases are then you have to double-check everything. Still, it's probably the best migration option if you rely on GHA.
Gitea also, I think.
Re: Moving from GitHub to Codeberg, for lazy people
#313Earlier quoted context omitted.
It is kinda incorrect and kinda correct. Codeberg allows you to create private repositories. However, their rules are clear that the intent of private repositories must be in support of Free software projects: https://docs.codeberg.org/getting-started/faq/#how-about-pri... , which for many people is effectively not allowing private repositories.
My reading is: Don't attempt to store your media (photos, music, videos, etc.) collection there, and you won't have any issues.
I don't like how it reads differently based on perspectives, they should be crystal clear on what's allowed and what's not, but when they say '...unhappy about...' as a statement, it feels kinda amateur to me although I'm pretty sure the operators must be way capable than me lol.
Re: Moving from GitHub to Codeberg, for lazy people
#314Earlier quoted context omitted.
There are multiple reasons why FTP by itself became obsolete. Some of them I can think of off the top of my head: 1) Passive mode. What is it and why do I need it? Well, you see, back in the old days, .... It took way too long for this critical "option" to become well supported and used by default. 2) Text mode. No, I don't want you to corrupt some of my files based on half-baked heuristics about what is and isn't a…
Why would you say FTP is obsolete? For what it's worth, I still use it (for bulk file transfer).
chrome and firefox dropped support for it 5 years or so ago, it has had a lot of security issues over the years, was annoying over NAT, and there are better options for secure bulk transfers (sftp, rsync, etc)
Re: Moving from GitHub to Codeberg, for lazy people
#315This repo also holds a lot of info about setting up two way mirrors between GitHub and Codeberg: https://codeberg.org/Recommendations/Mirror_to_Codeberg
Last commit is two years ago, but still a good overview.
Re: Moving from GitHub to Codeberg, for lazy people
#316Earlier quoted context omitted.
Custom-built on top of libgit2.
Not trying to be dismissive/snarky... But why?
I started developing it as a slim wrapper around Git to support my own needs. At the same time, it is essential to have rich features like pull requests/code review, so I started focusing on designing a tool that strikes an appropriate balance between being minimalistic and functional. One thing that I focus on is allowing users to disable any feature they don't need.
Re: Moving from GitHub to Codeberg, for lazy people
#317Earlier quoted context omitted.
I was shaking my head in disbelief when reading that part too. I mean, git's whole raison d'etre, back when it was introduced, was that you do not need online access to the repo server most of the time.
> I mean, git's whole raison d'etre, back when it was introduced, was that you do not need online access to the repo server most of the time. So what ? That's not how most people prefer to use it.
So those people are using the tool incorrectly, and would have a much better experience if they used it as designed. If everyone was running around using screwdriver handles to pound in nails, that wouldn't make it reasonable to say that any new screwdriver company has to have 5 lb handles.
Re: Moving from GitHub to Codeberg, for lazy people
#318> The by far nastiest part is CI. But that's the most important part. A repository without CI is basically dead. The biggest challenge of this era is automated verification, and proper CI infrastructure is essential. GitHub feels like what Hudson/Jenkins was some decades ago. Horrible, but the only one that did what it did. I run probably hundreds of dollars of CI on GitHub per month. Except I don't pay a cent for it…
You do not in any way need CI to make software. It's a helpful tool, not a requirement.
Re: Moving from GitHub to Codeberg, for lazy people
#319Earlier quoted context omitted.
Why would you say FTP is obsolete? For what it's worth, I still use it (for bulk file transfer).
chrome and firefox dropped support for it 5 years or so ago, it has had a lot of security issues over the years, was annoying over NAT, and there are better options for secure bulk transfers (sftp, rsync, etc)
I see, I assumed by ftp you also meant sftp.
Re: Moving from GitHub to Codeberg, for lazy people
#320> The by far nastiest part is CI. But that's the most important part. A repository without CI is basically dead. The biggest challenge of this era is automated verification, and proper CI infrastructure is essential. GitHub feels like what Hudson/Jenkins was some decades ago. Horrible, but the only one that did what it did. I run probably hundreds of dollars of CI on GitHub per month. Except I don't pay a cent for it…
You do not in any way need CI to make software. It's a helpful tool, not a requirement.
Don't put words on my mouth.