On the up side, stuff like this should encourage everyone to move their repos to self-hosted software that won't arbitrarily move your cheese around for dubious, non-technical reasons. It's far better to laugh at this sort of thing from a distance.
Announcement
Collapse
No announcement yet.
GitLab Will Now Default To "Main" For New Git Repositories
Collapse
X
-
Originally posted by squash View PostOn the up side, stuff like this should encourage everyone to move their repos to self-hosted software that won't arbitrarily move your cheese around for dubious, non-technical reasons. It's far better to laugh at this sort of thing from a distance.
Gitea - Git with a cup of tea! Painless self-hosted all-in-one software development service, including Git hosting, code review, team collaboration, package registry and CI/CD
- Likes 6
Comment
-
Originally posted by Brisse View PostInstead of arguing with the alt-right (which is pointless), I suggest to go on Y*uT*be and spend some time going through "Innuendo Studios" playlist called "The Alt-Right Playbook". It will be more satisfying and interesting than arguing with these trolls. It might even be educational. Highly recommended.
- Likes 2
Comment
-
Originally posted by squash View PostOn the up side, stuff like this should encourage everyone to move their repos to self-hosted software that won't arbitrarily move your cheese around for dubious, non-technical reasons.
- Likes 2
Comment
-
Originally posted by squash View PostOn the up side, stuff like this should encourage everyone to move their repos to self-hosted software that won't arbitrarily move your cheese around for dubious, non-technical reasons. It's far better to laugh at this sort of thing from a distance.
Gitea - Git with a cup of tea! Painless self-hosted all-in-one software development service, including Git hosting, code review, team collaboration, package registry and CI/CD
- Likes 3
Comment
-
Originally posted by archibald View Post
The change here is that they will suggest "main" as the default branch name for new git repositories, existing repositories will be unaffected. You can also decide to use whatever branch name you prefer - nobody is being forced to do anything.
- Likes 2
Comment
-
Originally posted by skeevy420 View PostNow scripts need lines to account for master and main depending on if the software was made pre or post woke. It's the woke version of compatibility profiles.
But again, no existing repos will be changed by this, so no scripts will break. Even if you want your scripts to stay hard-coded to use 'master' as the default branch name, you can choose 'master' as your default branch name when creating a new repository.
- Likes 1
Comment
-
Originally posted by access View PostLots of triggered snowflakes in this thread.
Good on GitLab. Perhaps I don't need this in my .gitconfig soon.
Code:[B]❯[/B] grep -A 1 init ~/.gitconfig [init] defaultBranch = main
Code:[init] defaultBranch = racism
Comment
Comment