At the moment, master is the default branch name both for git and at this gitea instance.
There is a config parameter that allows changing it in gitea.
Considering git itself seems to be in the middle of the discussion to change the default, what would you propose?
At the moment, `master` is the default branch name both for `git` and at this `gitea` instance.
There is a config parameter that allows changing it in gitea.
Considering `git` itself seems to be in the middle of the discussion to change the default, what would you propose?
This is a non-issue imo. The default branch has been called master from time immemorial and I see no reason to even consider changing it. This naming convention also predates git, or any other scm and is still in use in the industries from which it was borrowed.
This is a non-issue imo. The default branch has been called master from time immemorial and I see no reason to even consider changing it. This naming convention also predates git, or any other scm and is still in use in the industries from which it was borrowed.
This is a non-issue imo. The default branch has been called master from time immemorial and I see no reason to even consider changing it. This naming convention also predates git, or any other scm and is still in use in the industries from which it was borrowed.
while historically this has been true, the stance on the matter appears to be changing even in git, that is why I thought it's relevant to bring this up.
> This is a non-issue imo. The default branch has been called master from time immemorial and I see no reason to even consider changing it. This naming convention also predates git, or any other scm and is still in use in the industries from which it was borrowed.
while historically this has been true, the stance on the matter appears to be changing even in git, that is why I thought it's relevant to bring this up.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
At the moment,
masteris the default branch name both forgitand at thisgiteainstance.There is a config parameter that allows changing it in gitea.
Considering
gititself seems to be in the middle of the discussion to change the default, what would you propose?This is a non-issue imo. The default branch has been called master from time immemorial and I see no reason to even consider changing it. This naming convention also predates git, or any other scm and is still in use in the industries from which it was borrowed.
while historically this has been true, the stance on the matter appears to be changing even in git, that is why I thought it's relevant to bring this up.
keeping the default for now.
closing this, we'll see if we have to reopen in the future :D