新项目中的源代码控制 [英] Source control in new projects

问题描述

我在工作中独自处理一个项目，我知道最终它需要存储在我们的 SVN 中.我的问题是如果我从头开始，我该怎么做才能将它存储在 SVN 中?我是只提交稳定的完整构建还是在我觉得某个模块达到某个里程碑时才提交?

I'm working on a project by myself at work and I know eventually it will need to be stored in our SVN. My question is what do I do to store it in SVN if I'm starting from scratch? Do I only commit stable complete builds or commit when I feel a certain module reaches a certain milestone?

推荐答案

尽早并经常提交.在团队中工作时，这可以最大限度地减少冲突解决步骤.单独工作时，这也是一种很好的做法，这样您就有了一段历史，如果您发现自己走错了方向，您可以回滚过去.

Commit early and often. This minimizes conflict resolution steps when working in a team. It's also good practice when working alone so you have a history that you can roll back to if you find you've moved in a wrong direction.

这篇关于新项目中的源代码控制的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！