#194 Rename 'master' branches to something else

Closed
opened 7 months ago by lafnlab · 12 comments
lafnlab commented 7 months ago

Considering the global news of the past few weeks, many tech companies have been replacing legacy terms like 'master' to other terms line 'main' or 'primary'. Github is working on it. Is this something Codeberg plans on doing?

Considering the global news of the past few weeks, many tech companies have been replacing legacy terms like 'master' to other terms line 'main' or 'primary'. Github is [working on it](https://www.theregister.com/2020/06/15/github_replaces_master_with_main/). Is this something Codeberg plans on doing?
hw commented 7 months ago
Poster
Owner

Git allows arbitrary branch names, you are free to pick whatever you like ;)

There might be some UI defaults people might want to change, contributions and PRs very welcome.

Git allows arbitrary branch names, you are free to pick whatever you like ;) There might be some UI defaults people might want to change, contributions and PRs very welcome.
steko commented 7 months ago
Poster

This should be included in Gitea 1.11.6 and 1.12 https://github.com/go-gitea/gitea/pull/10803 (applies to new repository creation). It's already working on codeberg-test

immagine

I'm glad to see we quickly adopted this small but important change. I propose to change the default as well, e.g. to "main" or "trunk".

This should be included in Gitea 1.11.6 and 1.12 https://github.com/go-gitea/gitea/pull/10803 (applies to new repository creation). It's already working on codeberg-test ![immagine](/attachments/568ca8d1-72f9-460c-b3ad-3b6476762006) I'm glad to see we quickly adopted this small but important change. I propose to change the default as well, e.g. to "main" or "trunk".
hw commented 7 months ago
Poster
Owner

1.12 release candidate is already tested on https://codeberg-test.org, will launch here as soon it is stable.

There still seem to be some issues with db migration, we are looking into this (database upgrade very slow, implying potential downtime we would like to avoid during upgrade).

1.12 release candidate is already tested on https://codeberg-test.org, will launch here as soon it is stable. There still seem to be some issues with db migration, we are looking into this (database upgrade very slow, implying potential downtime we would like to avoid during upgrade).
Poster

Yes, it would be nice to change the default name, or add an account setting to set your own default.

Yes, it would be nice to change the default name, or add an account setting to set your own default.
hw commented 7 months ago
Poster
Owner

Easy: Just visit your repository settings page and choose a default you like:

Easy: Just visit your repository settings page and choose a default you like:
hw commented 7 months ago
Poster
Owner

(the change discussed above is merely adding the selection more prominently in the dialog for creating new repos;)

(the change discussed above is merely adding the selection more prominently in the dialog for creating new repos;)
ncc1988 commented 7 months ago
Poster

I think it is good if people have a relatively free choice how to name the default branch.

I think it is good if people have a relatively free choice how to name the default branch.
6543 commented 7 months ago
Poster
Collaborator
https://github.com/go-gitea/gitea/pull/11918
hw commented 7 months ago
Poster
Owner
https://codeberg.org/Codeberg/build-deploy-gitea/commit/3e82d542d5c8705b34645a6b318d8aa8f277bff2
steko commented 7 months ago
Poster

Great to see this change happen! It might be worth its own blog post?

Great to see this change happen! It might be worth its own blog post?
lafnlab commented 7 months ago
Poster

Thanks for pointing out that this can be done in Git. I didn't see the ability to create new branches in the Codeberg/Gitea interface, but was able to get Atom to do it, then in Codeberg I made the new branches as the defaults.

Small changes like these accumulate, and while they may not get rid of racism forever, they help make it less systemic.

Thanks for pointing out that this can be done in Git. I didn't see the ability to create new branches in the Codeberg/Gitea interface, but was able to get Atom to do it, then in Codeberg I made the new branches as the defaults. Small changes like these accumulate, and while they may not get rid of racism forever, they help make it less systemic.
hw commented 6 months ago
Poster
Owner

Closed by update to gitea-1.12

Closed by update to gitea-1.12
hw closed this issue 6 months ago
Sign in to join this conversation.
No Milestone
No Assignees
6 Participants
Notifications
Due Date

No due date set.

Dependencies

This issue currently doesn't have any dependencies.

Loading…
There is no content yet.