home.social

#shithub — Public Fediverse posts

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

  1. After now seeing the third(?) talk on how to work around #github #shithub shortcomings I wonder why we not start using something else...

    #rustweek #rustweek2026

  2. After now seeing the third(?) talk on how to work around #github #shithub shortcomings I wonder why we not start using something else...

    #rustweek #rustweek2026

  3. After now seeing the third(?) talk on how to work around #github #shithub shortcomings I wonder why we not start using something else...

    #rustweek #rustweek2026

  4. After now seeing the third(?) talk on how to work around #github #shithub shortcomings I wonder why we not start using something else...

    #rustweek #rustweek2026

  5. After now seeing the third(?) talk on how to work around #github #shithub shortcomings I wonder why we not start using something else...

    #rustweek #rustweek2026

  6. With all the people moving from #shithub to #codeberg I really get the feeling of "Lets jump from one Silo into another".

    Arguably a much better Silo, but a Silo still.

    It really is time for #forgejo to get federation abilities. Because the majority won't go to #sourcehut and (the proper) email based development scheme unfortunately.

    Or #radicle to succeeds. But I don't see this happen just yet unfortunately although it is really good already.

  7. #shithub amazes again:

    Ctrl-F for searching for something. Find it in the code.

    Hit <ESC>

    Page jumps to top.

    THANK YOU SHITHUB! #github

  8. @jer you forgot the #shithub tag, so I can make a end-of-year-best-of-shithub collection

  9. Why on earth has torvalds/linux LESS stars than awesome-selfhosted/awesome-selfhosted on #github #shithub ?

    👀

  10. It does not surprise me that #shithub does not feature `-o ci.skip` (via github.com/orgs/community/disc)

    ... because that does not increase any cashflow, does it? It does not help #microshit to push #aibullshit into everyones faces.

    So why would they support such an obvious feature?

  11. Re-reading #email patch workflow stuff and the #b4 and #publicinbox docs and ... maaan... that is the only true way of developing software together in large teams.

    I mean, I don't care for your 5 person project, do what you want.

    But for large projects, that really is the only way to develop that truly scales.

    Maybe, just maybe, #radicle can become the second way of doing that. Right now, it clearly is not (mainly because it is too young), but I still have hope!

    That said, #sourcehut is also really nice, but right now I like public-inbox a bit more. I guess you could combine the two, possibly?

    #git #github #shithub #gitlab #shitlab

  12. Re-reading #email patch workflow stuff and the #b4 and #publicinbox docs and ... maaan... that is the only true way of developing software together in large teams.

    I mean, I don't care for your 5 person project, do what you want.

    But for large projects, that really is the only way to develop that truly scales.

    Maybe, just maybe, #radicle can become the second way of doing that. Right now, it clearly is not (mainly because it is too young), but I still have hope!

    That said, #sourcehut is also really nice, but right now I like public-inbox a bit more. I guess you could combine the two, possibly?

    #git #github #shithub #gitlab #shitlab

  13. Re-reading #email patch workflow stuff and the #b4 and #publicinbox docs and ... maaan... that is the only true way of developing software together in large teams.

    I mean, I don't care for your 5 person project, do what you want.

    But for large projects, that really is the only way to develop that truly scales.

    Maybe, just maybe, #radicle can become the second way of doing that. Right now, it clearly is not (mainly because it is too young), but I still have hope!

    That said, #sourcehut is also really nice, but right now I like public-inbox a bit more. I guess you could combine the two, possibly?

    #git #github #shithub #gitlab #shitlab

  14. Re-reading #email patch workflow stuff and the #b4 and #publicinbox docs and ... maaan... that is the only true way of developing software together in large teams.

    I mean, I don't care for your 5 person project, do what you want.

    But for large projects, that really is the only way to develop that truly scales.

    Maybe, just maybe, #radicle can become the second way of doing that. Right now, it clearly is not (mainly because it is too young), but I still have hope!

    That said, #sourcehut is also really nice, but right now I like public-inbox a bit more. I guess you could combine the two, possibly?

    #git #github #shithub #gitlab #shitlab

  15. Re-reading #email patch workflow stuff and the #b4 and #publicinbox docs and ... maaan... that is the only true way of developing software together in large teams.

    I mean, I don't care for your 5 person project, do what you want.

    But for large projects, that really is the only way to develop that truly scales.

    Maybe, just maybe, #radicle can become the second way of doing that. Right now, it clearly is not (mainly because it is too young), but I still have hope!

    That said, #sourcehut is also really nice, but right now I like public-inbox a bit more. I guess you could combine the two, possibly?

    #git #github #shithub #gitlab #shitlab

  16. I cannot wrap my head around why #github #shithub would ALLOW a merge request if the pipelines do not run because they contain invalid #yaml

    What a bunch of shitheads, seriously!

  17. Finally glad to get that out of the way. I'm reworking my grid with the mini PCs I got the other day, but after that I'll clean the repo a bit.

    shithub.us/jmq/pain/HEAD/info.

    #9front #shithub

  18. "Patches sent to distribution lists remains the only widely used decentralized code review framework. RFC2822-conformant (“email”) messages adhere to an established standard that ensures high level of interoperability between systems, and it remains one of the remaining few truly decentralized communication platforms."

    This!

    (source: b4.docs.kernel.org/en/latest/m)

    #git #email #enshittification #github #shithub #gitlab #softwaredevelopment #programming #collaboration

  19. I began removing repos on #shithub which were already only @Codeberg mirrors.

    Even though #github tries to scare me removing stuff 😉 - staying there scares me even more… 🌬️ 💩

  20. And now #shithub notifies me again about my own comments on the topic. Thanks #microshit #github !

    Srsly, since #microsoft bought github, everything started to get worse.

  21. If your self hosted #shithub runner is not up to date, #github does not fail your CI.

    Instead, it simply does not run anymore and your PRs will get green CI marks and you get the ability to merge, although no CI ran.

    THIS IS WHY WE CAN'T HAVE NICE THINGS YOU FNNNGNGNGGGGGGGRRRR

  22. #shithub sending me notifications for my own comments again...

  23. It is an absolute shitmove of #shithub that actions with typos or bad #yaml do not run and the PR is marked as green anyways... but _valid_ actions, that _do_ run on other PRs?

  24. Hey #github - why do I receive notification mails, but there are no notifications in my #shithub inbox?

  25. For what exactly is githubstatus.com if "all operational", but a fucking action that normally runs for less than 1 sec took 15 minutes to start for me (so far...)?

    #shithub #github

  26. I wonder who made that aweful design decision that an invalid workflow file results in #githubactions to tell me that everything is green although no actions got executed.

    #github #shithub #baddesign #baddesignchoices

  27. Syntax error in #githubactions means that your CI is green.

    What the fuck is wrong with these people at #shithub #MicroShit ?

  28. Just released an initial version of masto9 my fedi client for #9front
    It’s mostly usable, at least I do, but far from complete.

    Grab it on #shithub shithub.us/julienxx/masto9/HEA
    or #sourcehut sr.ht/~julienxx/Masto9/

    Let me know how it went if you ever try it.

  29. If you submit PRs to my #github repositories that have been written with #chatGPT or #shithub #copilot, I will block you!