githubteacher / githubteacher/github-for-developers-sept-2015
Project Naming Conventions in GITHUB
未关闭
question
- 主要语言
- C
- 星标
- 12
- 派生
- 37
- PR 合并指标
- 30 天内没有已合并 PR
描述
We are migrating from perforce to GITHUB , we have a deeply nested structure in perforce and we cant follow the same in GITHUB.
Example
ProductName-ServiceName-Version-Public/Private-ArtifactName
example webs-subscription-v3-pub-signup.
Can we move this as is to GITHUB.
We also have a requirement where the same service can have multiple versions and each version is a totally different implementation and cannot have the same master repository.
Is introducing version numbers in the project naming conventions a good practice for the above mentioned use case.
贡献指南
这个仓库没有索引到贡献指南
评估
这个 Issue 还没有评估数据。