iOS - 在故事板中管理代码合并的最佳实践 [英] iOS - best practice for managing code merge in a storyboard

问题描述

在xcode故事板中与许多团队成员合并会产生许多冲突等。我需要一个策略来与20个团队成员共享故事板，但要避免与在故事板中合并代码相关联的噩梦。

Merging in a xcode storyboard with many team members can produce many conflicts etc. I need a strategy to share a storyboard with 20 team members but to avoid the nightmares associated with merging code in a storyboard.

我想在xcode中为每个团队设置一个单独的目标，但这并不好，因为我们都需要更新，所以有两个故事板并不是一个好习惯。

I thought of having a separate target per team in xcode but this doesn't do well as we all need the updates so having two story boards is not good practice.

我的代码库是继承的。它是一个分叉的项目，故事板很重。我认为更改为xib可能很困难（??）

my code base is inherited. its a forked project that is storyboard heavy already. I think changing to xib might be difficult (??)

推荐答案

查看这个教程明确暗示不使用故事板在团队合作的同时。

Check out this tutorial which clearly suggests not using a storyboard while working on team.

但是您可以将团队分成每个模块，并使用一些版本控制系统作为bitbucket或git来管理您的代码，借助多个故事板（单独的故事板用于单独的模块）。

But you can divide team into each module and use some versioning system as bitbucket or git to manage your code with the help of multiple storyboards(separate storyboard for separate module).

每天小心提交和拉动肯定会解决冲突。

这篇关于iOS - 在故事板中管理代码合并的最佳实践的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！