Conversation

Notices

1. Embed this notice
   feld (feld@bikeshed.party)'s status on Saturday, 06-May-2023 01:12:05 JST feld
   I wonder how many billions of dollars in salaries and electricity were wasted on engineers re-tooling their development/deployment processes to use "main" instead of "master" as the primary branch
   
   Not a single dollar of that effort reached the pockets of an African American and provided a tangible improvement to their lives. 99% of them don't even know it happened.
   • Embed this notice
     feld (feld@bikeshed.party)'s status on Saturday, 06-May-2023 01:14:23 JST feld

     in reply to
     a shitload of white people in tech are patting themselves on the back though
   • Embed this notice
     feld (feld@bikeshed.party)'s status on Saturday, 06-May-2023 01:16:53 JST feld

     in reply to

     • The Doctor
     people in tech all around the world decided to declare war on the git master branch.
     
     I'm sure there are still tools and scripts out there that are broken because they hardcoded to "master" lol
   • Embed this notice
     The Doctor (drwho@hackers.town)'s status on Saturday, 06-May-2023 01:16:54 JST The Doctor

     in reply to

     @feld Companies changed their remote names?

   • Embed this notice
     feld (feld@bikeshed.party)'s status on Saturday, 06-May-2023 02:00:46 JST feld

     in reply to

     • The Doctor
     every company using Github now has "main" as their default branch. They made changes to accommodate this.
     
     And git itself changed. So they had to follow, or auto-deploy new git configs everywhere that sets it back to "master"
   • Embed this notice
     The Doctor (drwho@hackers.town)'s status on Saturday, 06-May-2023 02:00:47 JST The Doctor

     in reply to

     @feld I don't know of any companies that actually changed that.

     Doesn't mean there aren't any, thoiugh.