我如何完全接近版本控制和核心数据模型？ [英] How can I sanely approach version control and Core Data models?

问题描述

当我们使用git将Core Data模型文件置于版本控制之下时，我们总是有一个可怕的时间合并更改 - 我们发现避免手动合并的唯一可靠的方法是在团队之间进行沟通阻止访问模型，而一个人进行必要的更改和推送，然后下一个人等
当然有一个更好的方式来处理这个，但作为一个git新手没有明显的解决方案。
任何建议？

When we put Core Data model files under version control with git, we always have a horrible time merging changes - the only sure fire way we've found to avoid having to merge in changes by hand is to communicate among the team to block off access to the model while one person makes their necessary changes and pushes, then the next person, etc. Surely there is a better way to handle this, but as a git novice no obvious solution comes to mind. Any suggestions?

推荐答案

据我所见，目前没有saner的方式，以不适合合并的格式存储。通常我做的就是你做什么，有一个人一次在模型上工作，以避免碰撞。

As far as I have seen, there is no saner way at this time because the model is stored in a format that does not lend itself to merging. Normally I do exactly what you do, have one person working on the model at a time to avoid collisions.

这篇关于我如何完全接近版本控制和核心数据模型？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！