推入所有本地GIT分支？最佳实践？ [英] PUSH all local GIT branches? Best Practice?

问题描述

所有本地创建的GIT分支是否应该每天推送到中央存储库？什么是最佳实践工作流程？

我们创建了一个GIT存储库来管理我们的大型电子商务网站，该网站由一个大型团队持续开发。 p>

中央存储库位于'Beanstalk'中，我们有三个主要分支，'prestaging'（master），'staging'和'production'。所有的开发工作都应该在当地完成并准备发布的时候合并到预先安排中。

我可以看到推动长期运营的分支机构也发展到了Beanstalk。然而，我们的一些团队倡导者将所有本地开发分支机构每天都推进到Beanstalk进行中或不进行;创造冗余。我认为随着时间的推移，这会使数百个分支机构的存储库变得混乱。什么是最佳做法？

解决方案

我不喜欢 所有分支 >所有用户。

不要混合：

• 出版工作流程 ：您选择发布的内容（推/拉到上游回购 ）


• 备份需要：使用 bundle（请参阅备份本地Git存储库） ，这样您只有一个文件可以复制到任何您想要的远程驱动器。

Should ALL locally created GIT branches be pushed to the central-repository on a daily basis? What is best-pracice workflow concerning this?

We created a GIT repository to manage our large e-commerce site, which is under continual development by a large team.

The central repository is at 'Beanstalk' and we have three primary branches, 'prestaging' (master), 'staging' and 'production'. All development should be merged into prestaging when it is completed locally and ready to be published.

I can see pushing long-running branches to Beanstalk as well. However some of our team advocates pushing ALL local development branches to Beanstalk on a daily basis in-progress or not; to create redundancy. I think this would clutter the repository with hundreds of branches over time. What is best practice?

解决方案

I prefer not polluting the central repo with all branches of all users.

Don't mix:

• publication workflow: what you choose to publish (push/pull to an upstream repo)
• backup need: use a bundle (See "Backup a Local Git Repository"), that way you have only one file to copy to any remote drive you want.

这篇关于推入所有本地GIT分支？最佳实践？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！