如何管理github上过时的分支 [英] how to manage obsolete branches on github

查看:220
本文介绍了如何管理github上过时的分支的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我通常会在专门的分支中开发我的代码的新功能,然后将它们合并到master中。

这个问题是在一段时间后,我有很多过时的分支正在混淆github界面,可能会有分支机构被积极开发。

有没有办法将它们归档,或者我应该删除它们,因为提交已经合并了?

解决方案

如果您已经合并了分支并且无需再开发它们,那么删除它们是安全的。您不会丢失任何提交,因为它们已被合并,现在存储在master中。



我只会建议离开您主动开发的分支


I usually develop new features of my codes in dedicated branches, then merge them to master.

The problem with this is that after some time I have a lot of obsolete branches that are cluttering the github interface, where there might be instead branches which are actively developed.

Is there a way to archive them somehow, or should I just delete them, as the commits have already been merged?

解决方案

If you have already merged branches and have no need to develop on them anymore, then it's safe to delete them. You don't loose any commit, as they have been merged and are now stored in master.

I would only propose to leave branches you actively develop

这篇关于如何管理github上过时的分支的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆