You must log in or register to comment.
- 46 minutes
They were successful because of VC funding, we were doomed from the start. VCs want one thing and one thing only, to back a Unicorn. Nothing else matters to them.
- 5 hours
I really wish more FOSS projects would move off of GitHub. It feels wrong just having an account just so I can contribute. Hopefully horrible “features” like this encourages others to migrate.
- 4 hours
> Decentralized protocol implemented by Torvalds himself
> Community gravitates around one decent website
> Microsoft buys that websiteThis is why we can’t have nice things.
5 hoursI have a library that has over 2 Million downloads in pip. How do you switch from github to codeberg (or any other git)? I just dont want to break things for everyone :)
- 4 hours
You can start by moving your development workflows (pull requests, issue tracking, etc.) to something like codeberg. You can continue publishing your PyPI package from Github by just pushing your code from codeberg to Github.
Eventually you can also move the publishing pipeline over as well. I don’t know how complicated your library is, of course, but in simplest cases it’s a matter of rewriting a config file in a slightly different way.
- uuj8za@piefed.socialEnglish3 hours
I mean, if Zig and Guix can do it. It’s possible.
I’m in a similar boat. So far:
- I started mirroring GitHub to Codeberg
- I added CI to Codeberg
Next I gotta update the readme on GitHub telling everyone that I’m going to move to Codeberg. I’ll let that sit for a few months.
Also, I gotta update consumers like homebrew to consume from Codeberg instead.
I was gonna close/merge any open PRs on GitHub.
Issues, I’m not totally sure about. I thought I read there was a way to migrate those. Although, I’m kiiinda ok with starting fresh… not totally sure this part needs more thought.
Once the Codeberg repo is ready, I’ll make the GitHub repo read-only, with the readme pointing to Codeberg.
Way, way, way down the line, I’d consider deleting the GitHub repo (and finally my account).
I’m OK with breaking things. I’m gonna try my hardest to not break stuff, but I’m not going to let the fear of breaking stuff prevent me from getting on ShitHub by Macroslop.
How did you get the CI working in codeberg? last time I checked, you had to get permission to do so(?). I would love to switch when I have time.
- uuj8za@piefed.socialEnglish3 hours
You do have to ask for permission. https://docs.codeberg.org/ci/
Asking permission involves creating an issue on the
Codeberg-e.V./requestsrepo: https://codeberg.org/Codeberg-e.V./requests/issues/new?template=ISSUE_TEMPLATE%2FWoodpecker-CI.yamlHere’s an example issue asking permission for CI: https://codeberg.org/Codeberg-e.V./requests/issues/1663
They get back to you fairly quickly. I think the main thing they check for is if your project is FOSS. They don’t seem very strict otherwise.
After you get permission, you can go to https://ci.codeberg.org/login to access CI.
You’ll also need to create a
.woodpeckerfolder in your repo.Woodpecker docs are here: https://woodpecker-ci.org/docs/usage/intro
# .woodpecker/my-first-workflow.yaml when: - event: push branch: main steps: - name: build image: debian commands: - echo "This is the build step" - echo "binary-data-123" > executable - name: a-test-step image: golang:1.16 commands: - echo "Testing ..." - ./executable
- SpikesOtherDog@ani.socialEnglish3 hours
I think you would clone the repo and continue with codeberg. Announce wherever you can, and continue any new work at the new repo.
- 4 hours
explain how you contribute with out an account? is there a hosting service that lets you do that?
- Ephera@lemmy.mlEnglish3 hours
In case, you’re not aware, you can also email the dev. You can code up your commits as normal and then use e.g.
git format-patch -3to put the last 3 commits patch files. You can then attach those files to an e-mail and the dev can apply those patches withgit am.It takes a bit of playing around, but it’s actually really easy.
The Linux kernel, one of the most complex projects on the planet, develops like this. They also created very good documentation: https://git-send-email.io/
- 3 hours
I currently have a GitHub account in order to contribute to projects hosted on GitHub, because I don’t think there is currently a way possible to do thinks like open up an issue without an account.
- 6 hours
This is fucking hilarious.
It rewrites the description so unless you view the in app edit history it looks like you are endorsing this ad!
Who the fuck shipped this lol
- Ephera@lemmy.mlEnglish3 hours
Yeah, I might block a contributor on sight, if they post something like that.
March 30, 2026 @ 10:45 AM EST: Martin Woodward, Vice President of Developer Relations at GitHub, confimed that Copilot was injecting product tips into pull requests but that the feature has been disabled following feedback.
They posted an update to the article about this recent update. After feedback, they decided to disable this feature.
- TachyonTele@piefed.socialEnglish5 hours
It’ll be back. They’ll just wait a little longer to fully implement it.
Eventually it will be This feature can only be disabled on Enterprise or Pro+ plans
- 6 hours
Yeah, this was always the next obvious booster stage on the Slop Rocket.
Not even labeled as an ad/sponsored content/influenced “tip”/suggestion.
- hperrin@lemmy.caEnglish6 hours
I’m in the process of switching to my own Forgejo instance. It’s been pretty easy so far.
