home.social

#giveupgithub — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #giveupgithub, aggregated by home.social.

  1. We've created a infrastructure cost report including donations from the creation of our platform until today. Read more at forum.codefloe.com/t/2026-05-0

    #codefloe #giveUpGitHub #forgejo

  2. Our hosted #renovate bot now runs via the mogenius/renovate-operator (github.com/mogenius/renovate-o).

    This enables webhook-based support, i.e. clicking the checkboxes in the renovate dashboard and PR actions now have an effect!

    Read more here: forum.codefloe.com/t/2026-03-3

    #codefloe #forgejo #renovate #giveUpGitHub

  3. Our hosted #renovate bot now runs via the mogenius/renovate-operator (github.com/mogenius/renovate-o).

    This enables webhook-based support, i.e. clicking the checkboxes in the renovate dashboard and PR actions now have an effect!

    Read more here: forum.codefloe.com/t/2026-03-3

    #codefloe #forgejo #renovate #giveUpGitHub

  4. Our hosted #renovate bot now runs via the mogenius/renovate-operator (github.com/mogenius/renovate-o).

    This enables webhook-based support, i.e. clicking the checkboxes in the renovate dashboard and PR actions now have an effect!

    Read more here: forum.codefloe.com/t/2026-03-3

    #codefloe #forgejo #renovate #giveUpGitHub

  5. Our hosted #renovate bot now runs via the mogenius/renovate-operator (github.com/mogenius/renovate-o).

    This enables webhook-based support, i.e. clicking the checkboxes in the renovate dashboard and PR actions now have an effect!

    Read more here: forum.codefloe.com/t/2026-03-3

    #codefloe #forgejo #renovate #giveUpGitHub

  6. I am tackeling my next project in moving away from #BigTech and #USTech companies. This one is one that is really hard for me, and that pains me a bit: I'm moving away from #GitHub - it's hard for me, because I've been brought up with #SVN and instantly fell in love with #DVCS, and with #git I instantly also started using GitHub. And I **really** used it like their slogan suggested: Like "facebook for programmers". I followed friends and colleagues, followed projects I loved and people that seemd interesting to me, and even had a couple of discussions that started with a commit or new repository on Github. Plus, I love their mascot and have a huge amount of stickers featuring #Octocat - to me GitHub was a crucial part of my programming hobby and upbringing.

    However, since #Microsoft accquired it, my engagement got less, even though I stayed, because no other solution at that time was remotely what I wanted and loved about GitHub.

    Since then, lots of things have happend; GitHub fired people that spoke out against the capitol attack, it does business with ICE, and is now monetizing the works of millions of open source developers with their integration of AI in GitHub that you never agreed to and cannot opt out of. And GitHub's parent company openly supports Trump, and meddles in international juristriction and politics by blocking political enemies of the Trump regime from their accounts (i.e. the E-Mail account of ICC Prosecutors).

    I think I won't delete my old GitHub account; but active and new repositories will be moved to @Codeberg - I am not sure if it is the right home for me, or if I long-term will be hosting my own @gitea or @forgejo instance; but for a start I think it is the right thing to do, and as I am currently working on something I would like to put under versioning, now is the best time to do it. So if you want to follow along, here is my new repository host:

    codeberg.org/pygospa

    #BoycottBigTech #UnplugTrump #privacy #security #souverein #NoAI #AiMisuse #GiveUpGitHub #codeberg #forgejo

  7. I am tackeling my next project in moving away from #BigTech and #USTech companies. This one is one that is really hard for me, and that pains me a bit: I'm moving away from #GitHub - it's hard for me, because I've been brought up with #SVN and instantly fell in love with #DVCS, and with #git I instantly also started using GitHub. And I **really** used it like their slogan suggested: Like "facebook for programmers". I followed friends and colleagues, followed projects I loved and people that seemd interesting to me, and even had a couple of discussions that started with a commit or new repository on Github. Plus, I love their mascot and have a huge amount of stickers featuring #Octocat - to me GitHub was a crucial part of my programming hobby and upbringing.

    However, since #Microsoft accquired it, my engagement got less, even though I stayed, because no other solution at that time was remotely what I wanted and loved about GitHub.

    Since then, lots of things have happend; GitHub fired people that spoke out against the capitol attack, it does business with ICE, and is now monetizing the works of millions of open source developers with their integration of AI in GitHub that you never agreed to and cannot opt out of. And GitHub's parent company openly supports Trump, and meddles in international juristriction and politics by blocking political enemies of the Trump regime from their accounts (i.e. the E-Mail account of ICC Prosecutors).

    I think I won't delete my old GitHub account; but active and new repositories will be moved to @Codeberg - I am not sure if it is the right home for me, or if I long-term will be hosting my own @gitea or @forgejo instance; but for a start I think it is the right thing to do, and as I am currently working on something I would like to put under versioning, now is the best time to do it. So if you want to follow along, here is my new repository host:

    codeberg.org/pygospa

    #BoycottBigTech #UnplugTrump #privacy #security #souverein #NoAI #AiMisuse #GiveUpGitHub #codeberg #forgejo

  8. I am tackeling my next project in moving away from #BigTech and #USTech companies. This one is one that is really hard for me, and that pains me a bit: I'm moving away from #GitHub - it's hard for me, because I've been brought up with #SVN and instantly fell in love with #DVCS, and with #git I instantly also started using GitHub. And I **really** used it like their slogan suggested: Like "facebook for programmers". I followed friends and colleagues, followed projects I loved and people that seemd interesting to me, and even had a couple of discussions that started with a commit or new repository on Github. Plus, I love their mascot and have a huge amount of stickers featuring #Octocat - to me GitHub was a crucial part of my programming hobby and upbringing.

    However, since #Microsoft accquired it, my engagement got less, even though I stayed, because no other solution at that time was remotely what I wanted and loved about GitHub.

    Since then, lots of things have happend; GitHub fired people that spoke out against the capitol attack, it does business with ICE, and is now monetizing the works of millions of open source developers with their integration of AI in GitHub that you never agreed to and cannot opt out of. And GitHub's parent company openly supports Trump, and meddles in international juristriction and politics by blocking political enemies of the Trump regime from their accounts (i.e. the E-Mail account of ICC Prosecutors).

    I think I won't delete my old GitHub account; but active and new repositories will be moved to @Codeberg - I am not sure if it is the right home for me, or if I long-term will be hosting my own @gitea or @forgejo instance; but for a start I think it is the right thing to do, and as I am currently working on something I would like to put under versioning, now is the best time to do it. So if you want to follow along, here is my new repository host:

    codeberg.org/pygospa

    #BoycottBigTech #UnplugTrump #privacy #security #souverein #NoAI #AiMisuse #GiveUpGitHub #codeberg #forgejo

  9. I am tackeling my next project in moving away from #BigTech and #USTech companies. This one is one that is really hard for me, and that pains me a bit: I'm moving away from #GitHub - it's hard for me, because I've been brought up with #SVN and instantly fell in love with #DVCS, and with #git I instantly also started using GitHub. And I **really** used it like their slogan suggested: Like "facebook for programmers". I followed friends and colleagues, followed projects I loved and people that seemd interesting to me, and even had a couple of discussions that started with a commit or new repository on Github. Plus, I love their mascot and have a huge amount of stickers featuring #Octocat - to me GitHub was a crucial part of my programming hobby and upbringing.

    However, since #Microsoft accquired it, my engagement got less, even though I stayed, because no other solution at that time was remotely what I wanted and loved about GitHub.

    Since then, lots of things have happend; GitHub fired people that spoke out against the capitol attack, it does business with ICE, and is now monetizing the works of millions of open source developers with their integration of AI in GitHub that you never agreed to and cannot opt out of. And GitHub's parent company openly supports Trump, and meddles in international juristriction and politics by blocking political enemies of the Trump regime from their accounts (i.e. the E-Mail account of ICC Prosecutors).

    I think I won't delete my old GitHub account; but active and new repositories will be moved to @Codeberg - I am not sure if it is the right home for me, or if I long-term will be hosting my own @gitea or @forgejo instance; but for a start I think it is the right thing to do, and as I am currently working on something I would like to put under versioning, now is the best time to do it. So if you want to follow along, here is my new repository host:

    codeberg.org/pygospa

    #BoycottBigTech #UnplugTrump #privacy #security #souverein #NoAI #AiMisuse #GiveUpGitHub #codeberg #forgejo

  10. I am tackeling my next project in moving away from #BigTech and #USTech companies. This one is one that is really hard for me, and that pains me a bit: I'm moving away from #GitHub - it's hard for me, because I've been brought up with #SVN and instantly fell in love with #DVCS, and with #git I instantly also started using GitHub. And I **really** used it like their slogan suggested: Like "facebook for programmers". I followed friends and colleagues, followed projects I loved and people that seemd interesting to me, and even had a couple of discussions that started with a commit or new repository on Github. Plus, I love their mascot and have a huge amount of stickers featuring #Octocat - to me GitHub was a crucial part of my programming hobby and upbringing.

    However, since #Microsoft accquired it, my engagement got less, even though I stayed, because no other solution at that time was remotely what I wanted and loved about GitHub.

    Since then, lots of things have happend; GitHub fired people that spoke out against the capitol attack, it does business with ICE, and is now monetizing the works of millions of open source developers with their integration of AI in GitHub that you never agreed to and cannot opt out of. And GitHub's parent company openly supports Trump, and meddles in international juristriction and politics by blocking political enemies of the Trump regime from their accounts (i.e. the E-Mail account of ICC Prosecutors).

    I think I won't delete my old GitHub account; but active and new repositories will be moved to @Codeberg - I am not sure if it is the right home for me, or if I long-term will be hosting my own @gitea or @forgejo instance; but for a start I think it is the right thing to do, and as I am currently working on something I would like to put under versioning, now is the best time to do it. So if you want to follow along, here is my new repository host:

    codeberg.org/pygospa

    #BoycottBigTech #UnplugTrump #privacy #security #souverein #NoAI #AiMisuse #GiveUpGitHub #codeberg #forgejo

  11. New feature: Hosted container registry proxy caches for use within CodeFloe CI. This avoids hitting pull rate limits from common registries such as docker.io or ghcr.io.

    Read more in the announcement post: forum.codefloe.com/t/exclusive

    #codefloe #forgejo #giveUpGitHub #cicd #codeberg

  12. r6d8: Nach nem Lychee-URL-Check und der Migration von meinem lab-of-labs nach #codeberg waren alle 57 Links wieder ok. Danach hab ich mein #github #jekyll-script auf marked.min.js umgestellt. Somit entfällt der md -> html Build Step. Angenehm.

    Mal schauen wie sich der #OpenGraph Header nun anfühlt.

    dbt4u.codeberg.page/lab-of-lab

    \__
    #100DaysOfCode #OpenSource #giveupgithub #didit #diday

  13. Naty @eclecticpassions ·

    [Shameless plug] I've written about migrating my Hugo to Sourcehut and Bunny, leaving GitHub. If you're thinking of switching, you can check it out here:
    burgeonlab.com/blog/hosting-st

    And if you're interested in trying out Bunny as your static hosting provider or Cloudflare alternative, you can show your support by using this referral code (I get a commission if you become a paying member):

    bunny.net/?ref=k4vc3x5108

    Thank you!

  14. Naty @eclecticpassions ·

    Great move away from GitHub, as shared by @cass! 🥳

    I read her post via my RSS feed and saw my post about switching to Bunny mentioned (thanks for linking my guide, Cassie)! If you're still using GitHub for your source codes or for hosting your free static site—definitely reconsider alternatives.

    cassie.ink/friendship-ended-wi

  15. Naev has migrated from GitHub to Codeberg.
    We do not wish to be complicit in what Microsoft has been supporting and pushing, from the obnoxious "vibe coding" to literal genocide and elon musk's "mecha hitler" chatbot.

    Blarg post: naev.org/blarg/2025-09-30_au_r
    Migrated repo: codeberg.org/naev/naev

    (The GitHub repository will just be a mirror now.)

    #naev #foss #gamedev #github #codeberg #giveupgithub

  16. Time to make a move? #GiveUpGitHub

    New How-to Guide on #BurgeonLab

    burgeonlab.com/blog/migrate-gi

    It's a thorough guide of switching from an automated CI static site deployment workflow using GitHub Pages & GitHub Actions 🔄 to SourceHut Git and Builds + hosting on Bunny.net Storage & Bunny CDN.

    #techguides #blog #blogging #blogpost #hugo #cicd #CDN #bunnycdn #bunnynet #github #sourcehut #githubactions #githubpages #srht

  17. Naty @eclecticpassions ·

    Time to make a move?

    New How-to Guide on

    burgeonlab.com/blog/migrate-gi

    It's a thorough guide of switching from an automated CI static site deployment workflow using GitHub Pages & GitHub Actions 🔄 to SourceHut Git and Builds + hosting on Bunny.net Storage & Bunny CDN.

  18. Time to make a move? #GiveUpGitHub

    New How-to Guide on #BurgeonLab

    burgeonlab.com/blog/migrate-gi

    It's a thorough guide of switching from an automated CI static site deployment workflow using GitHub Pages & GitHub Actions 🔄 to SourceHut Git and Builds + hosting on Bunny.net Storage & Bunny CDN.

    #techguides #blog #blogging #blogpost #hugo #cicd #CDN #bunnycdn #bunnynet #github #sourcehut #githubactions #githubpages #srht

  19. Time to make a move? #GiveUpGitHub

    New How-to Guide on #BurgeonLab

    burgeonlab.com/blog/migrate-gi

    It's a thorough guide of switching from an automated CI static site deployment workflow using GitHub Pages & GitHub Actions 🔄 to SourceHut Git and Builds + hosting on Bunny.net Storage & Bunny CDN.

    #techguides #blog #blogging #blogpost #hugo #cicd #CDN #bunnycdn #bunnynet #github #sourcehut #githubactions #githubpages #srht

  20. Time to make a move? #GiveUpGitHub

    New How-to Guide on #BurgeonLab

    burgeonlab.com/blog/migrate-gi

    It's a thorough guide of switching from an automated CI static site deployment workflow using GitHub Pages & GitHub Actions 🔄 to SourceHut Git and Builds + hosting on Bunny.net Storage & Bunny CDN.

    #techguides #blog #blogging #blogpost #hugo #cicd #CDN #bunnycdn #bunnynet #github #sourcehut #githubactions #githubpages #srht

  21. It took longer than expected for me (a day on and off) to get #sourcehut builds workflow to work with Bunny's SFTP limitations but I got it working! This is definitely going into a blog post! Really happy it worked out. Sourcehut Git repo + Builds + Bunny.net Storage + CDN replacing GitHub Git repo + Actions + Pages!

    #github #githubpages #githubactions #srht #bunnynet #bunnycdn #bunnystorage #GiveUpGitHub #staticsite #hosting #cdn

  22. Naty @eclecticpassions ·

    It took longer than expected for me (a day on and off) to get builds workflow to work with Bunny's SFTP limitations but I got it working! This is definitely going into a blog post! Really happy it worked out. Sourcehut Git repo + Builds + Bunny.net Storage + CDN replacing GitHub Git repo + Actions + Pages!

  23. It took longer than expected for me (a day on and off) to get #sourcehut builds workflow to work with Bunny's SFTP limitations but I got it working! This is definitely going into a blog post! Really happy it worked out. Sourcehut Git repo + Builds + Bunny.net Storage + CDN replacing GitHub Git repo + Actions + Pages!

    #github #githubpages #githubactions #srht #bunnynet #bunnycdn #bunnystorage #GiveUpGitHub #staticsite #hosting #cdn

  24. It took longer than expected for me (a day on and off) to get #sourcehut builds workflow to work with Bunny's SFTP limitations but I got it working! This is definitely going into a blog post! Really happy it worked out. Sourcehut Git repo + Builds + Bunny.net Storage + CDN replacing GitHub Git repo + Actions + Pages!

    #github #githubpages #githubactions #srht #bunnynet #bunnycdn #bunnystorage #GiveUpGitHub #staticsite #hosting #cdn

  25. It took longer than expected for me (a day on and off) to get #sourcehut builds workflow to work with Bunny's SFTP limitations but I got it working! This is definitely going into a blog post! Really happy it worked out. Sourcehut Git repo + Builds + Bunny.net Storage + CDN replacing GitHub Git repo + Actions + Pages!

    #github #githubpages #githubactions #srht #bunnynet #bunnycdn #bunnystorage #GiveUpGitHub #staticsite #hosting #cdn

  26. New post on #BurgeonLab ✍️

    ➡️ burgeonlab.com/blog/hosting-st

    Finally decided to take my first actions on migrating away from GitHub.com (#GiveUpGitHub) by moving my burgeonlab.com static blog out of GitHub Pages to Bunny.net Storage + CDN.

    Also, I've decided to go for @sourcehut as my Git repo host—but that warrants its own post.

    #blogging #blogs #blog #hugo #srht #weblog #smallweb #github #sourcehut #bunnycdn #bunnynet #staticsite #webhosting #githubpages

  27. Naty @eclecticpassions ·

    New post on ✍️

    ➡️ burgeonlab.com/blog/hosting-st

    Finally decided to take my first actions on migrating away from GitHub.com () by moving my burgeonlab.com static blog out of GitHub Pages to Bunny.net Storage + CDN.

    Also, I've decided to go for @sourcehut as my Git repo host—but that warrants its own post.

  28. New post on #BurgeonLab ✍️

    ➡️ burgeonlab.com/blog/hosting-st

    Finally decided to take my first actions on migrating away from GitHub.com (#GiveUpGitHub) by moving my burgeonlab.com static blog out of GitHub Pages to Bunny.net Storage + CDN.

    Also, I've decided to go for @sourcehut as my Git repo host—but that warrants its own post.

    #blogging #blogs #blog #hugo #srht #weblog #smallweb #github #sourcehut #bunnycdn #bunnynet #staticsite #webhosting #githubpages

  29. New post on #BurgeonLab ✍️

    ➡️ burgeonlab.com/blog/hosting-st

    Finally decided to take my first actions on migrating away from GitHub.com (#GiveUpGitHub) by moving my burgeonlab.com static blog out of GitHub Pages to Bunny.net Storage + CDN.

    Also, I've decided to go for @sourcehut as my Git repo host—but that warrants its own post.

    #blogging #blogs #blog #hugo #srht #weblog #smallweb #github #sourcehut #bunnycdn #bunnynet #staticsite #webhosting #githubpages

  30. New post on #BurgeonLab ✍️

    ➡️ burgeonlab.com/blog/hosting-st

    Finally decided to take my first actions on migrating away from GitHub.com (#GiveUpGitHub) by moving my burgeonlab.com static blog out of GitHub Pages to Bunny.net Storage + CDN.

    Also, I've decided to go for @sourcehut as my Git repo host—but that warrants its own post.

    #blogging #blogs #blog #hugo #srht #weblog #smallweb #github #sourcehut #bunnycdn #bunnynet #staticsite #webhosting #githubpages

  31. My git forges accounts:
    #radiostudent #gitlab (selfhosted)
    KDE gitlab,
    #kompot #forgejo (selfhosted)
    #codeberg forgejo
    #github for work (#giveUpGithub)
    #sourcehut (didn't pay but I ❤️ that project )

    I had #bitbucket but lost credentials (I don't even miss). There are probably some uknown unknowns as well. Can't w8 for forge federation.

  32. @neilernst @twitwi @gvwilson @Yoric

    Overleaf software is apparently licensed under a core-premium model.

    core: The FOSS version is AGPLv3 [1] (on #GiveUpGitHub). #Ouvaton 's instance of Overleaf-the-software [2] runs the AGPL software: users *must* be informed that they have access to the free-licensed software.

    premium: The Overleaf-the-organisation version is (apparently) proprietary. No obligation to inform users about the AGPL.

    [1] github.com/overleaf/overleaf

    [2] latex.ouvaton.coop

  33. @neilernst @twitwi @gvwilson @Yoric

    Overleaf software is apparently licensed under a core-premium model.

    core: The FOSS version is AGPLv3 [1] (on #GiveUpGitHub). #Ouvaton 's instance of Overleaf-the-software [2] runs the AGPL software: users *must* be informed that they have access to the free-licensed software.

    premium: The Overleaf-the-organisation version is (apparently) proprietary. No obligation to inform users about the AGPL.

    [1] github.com/overleaf/overleaf

    [2] latex.ouvaton.coop

  34. @neilernst @twitwi @gvwilson @Yoric

    Overleaf software is apparently licensed under a core-premium model.

    core: The FOSS version is AGPLv3 [1] (on #GiveUpGitHub). #Ouvaton 's instance of Overleaf-the-software [2] runs the AGPL software: users *must* be informed that they have access to the free-licensed software.

    premium: The Overleaf-the-organisation version is (apparently) proprietary. No obligation to inform users about the AGPL.

    [1] github.com/overleaf/overleaf

    [2] latex.ouvaton.coop

  35. @neilernst @twitwi @gvwilson @Yoric

    Overleaf software is apparently licensed under a core-premium model.

    core: The FOSS version is AGPLv3 [1] (on #GiveUpGitHub). #Ouvaton 's instance of Overleaf-the-software [2] runs the AGPL software: users *must* be informed that they have access to the free-licensed software.

    premium: The Overleaf-the-organisation version is (apparently) proprietary. No obligation to inform users about the AGPL.

    [1] github.com/overleaf/overleaf

    [2] latex.ouvaton.coop

  36. @wildrose_dev Congratulations on publishing your freedom-respecting code! And I'm delighted to see you deliberately chose a freedom-respecting forge, #Codeberg, as its public home! You resisted the urge to carelessly feed it to Microsoft (github) like the common people do. Your vote for freedom matters. In case you're interested in that angle: https://wrily.foad.me.uk/foss-apps-live-in-foss-forges .

    #GiveUpGithub #useOpenTools #Codeberg
  37. What's your favourite #FreeSoftware that is #NotOnGitHub (or on other proprietary code forges like #GitLab.com)?

    Let us know in the comments! Feel free to also share code from other #Forgejo instances, #Sourcehut or other platforms.

    #FreeLibreSoftware #LibreSoftware #Opensource #FLOSS #FOSS #GiveUpGithub #GitHub

  38. Irregular reminder to anyone who needs to hear it:

    Platforms like #GitHub are not locking out young people due to legal requirements, but due to commercial interests.

    #GiveUpGitHub today and stop #adultism!

  39. @itsfoss

    We should move away from github and here is why: https://sfconservancy.org/GiveUpGitHub/

    As far as I understand publishing docker images should also be possible woth gitea, forgejo and codeberg. I haven’t tried myself.

    https://docs.gitea.io/en-us/packages/container/

    Forgejo is a “soft” fork of Gitea with a focus on scaling, federation and privacy under the umbrella of codeberg.

    https://forgejo.org/

    Those popular projects that do want to self host might want to use a CDN to reduce costs.

    Codeberg and sr.ht are alternatives for those who do not want to self-host. I am not sure if it is easy to use sr.ht for publishing docker images.

    https://codeberg.org https://sr.ht/

    Towards a federated future for software forges.

    NLnet supports the ForgeFed project and forgejo is implementing their protocol. https://nlnet.nl/project/ForgeFed-RPC/

    ForgeFed is a federation protocol for software forges and code collaboration tools for the software development lifecycle and ecosystem. ForgeFed is an ActivityPub extension.

    #srht #codeberg #nlnet #docker #gitea #forgejo #forgefed #giveupgithub

  40. @downey I am on board with the movement to #GiveUpGithub! I have already transitioned many (though not all of my older, semi-abandoned) repos to #Debian's #salsa service, which is based on #FLOSS #Gitlab and not limited to Debian projects. @Codeberg is another common choice and I would heartily recommend both.

    My most recent #FreeSoftware project, #filespooler, has never had a Github presence of any kind. salsa.debian.org/jgoerzen/file