我应该如何使用git组织多个相关的应用程序？ [英] How should I organize multiple related applications using git?

问题描述

我正在开始一个项目，该项目将包含一个Ruby on Rails Web应用程序，一个Android应用程序，一个iOS应用程序以及这些项目的营销网站。我不太确定我想如何在源代码控制中构造这个。

我使用git（和GitHub），我想我想要所有的因为我想在GitHub上使用wiki和问题列表，而不需要在GitHub上安装很多独立的项目。但是，在我看来，将每个应用程序放在其自己的存储库中会更简单。

这里有哪些注意事项？什么是最好的方法？这里有一个正确的方法吗？我认为每个项目都有一个存储库是最好的选择。我了解维基和问题的相关问题 - 除了主存储库（可能是网站或其他网站）之外，没有任何东西可以阻止它们被禁用，并且可以告诉用户在自述文件中提供信息和编写错误的地方。

但是我认为您需要针对每个项目都有问题跟踪器：他们可能会有不同的生命周期，同样的人不会参与等等。对于大项目来说很常见，因为它们将自己拆分为更小的项目，更容易维护。

我无法想象只有一个存储库的原因，当您的项目已经由几个明显的子项目组成。

I'm beginning work on a project that will consist of a Ruby on Rails web application, an Android application, an iOS application, and a marketing website for these projects. I'm not quite sure how I want to structure this in source control.

I'm using git (and GitHub) and I'm thinking I want all of the code in a single repository because I want to make use of the wiki and issues lists on GitHub without having a lot of separate projects to go to on GitHub. However, it seems to me like it would be simpler to have each application be in its own repository.

What are the considerations here? What's the best approach? Is there a "correct" approach here?

解决方案

I think having a repository per project is the best option to go. I understand the issue about wikis and issues - nothing prevents from from disabling them except on the main repository (which could be the website, or else), and to tell users in the readme where to go for informations and to file bugs.

But I think that you'll want to have issues tracker for each project : they'll probably have different life cycles, the same people won't be involved, etc. It's pretty common for big projects to split themselves into smaller ones, easier to maintain.

I can't think of a reason good enough for having only one repository, when your project is already consisting of several and obvious subprojects.

这篇关于我应该如何使用git组织多个相关的应用程序？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！