Rename "master" branches?

未关闭
#2 6 条评论 2 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
20/100
Issue 类型
功能
描述清晰度
需要澄清
活跃度
停滞
技术栈
git, github
领域
release

调研方向

Read the discussion in this issue about renaming the project’s default branch and preserving old file links with Git symbolic refs. First determine whether the project has chosen a replacement name and whether GitHub’s default branch changes affect its repositories. The issue does not specify a change to make or a completion criterion; it needs a maintainer decision before implementation.

由索引模型根据 Issue 内容生成。

描述

In the wake of recent events, several developers have chosen to rename the "master" branches on their projects, and GitHub has announced they will be changing the default branch name as well (although they haven't announced to what). It seems like "main", "develop", and "trunk" are all popular options.

Should we consider doing the same?

One problem with renaming branches is it breaks all existing links to files within repositories, however it appears that can be worked around via the use of git symrefs which allow the old name to point to the new name:

https://twitter.com/mountain_ghosts/status/1274060788580388868

主要语言
没有语言数据
星标
13
派生
4
平均合并
41 分钟
30 天内合并 PR
1

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

RustCrypto/meta 的其他 Issue

查看 RustCrypto/meta 的全部 Issue

相似的 Issue

更多 Release Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。