When saving the storyboard and committing the changes to git, the chances are good that the whole
section will be removed from or added to source co
In my experience the removal only happens if you open the storyboard and have class existence related errors. An example of this is opening the storyboard while a merge conflict is not yet resolved. One or more classes might not be parse-able. In this case Interface builder seems to be removing the entire section and not only the offending class.
For me it is easily fixed by opening the storyboard again after the patch is ready in case i see the removal. If all problems are resolved, the section is regenerated. If it isn't, it means I have a problem with project settings and i shouldn't be committing anyways.
(this answer is based personal experience, and is not a formal one)
The classes
section in the .storyboard
xml file lists all the view controllers you have in your project in order to
I guess this section is a cache, being retired when both of the two uses listed above haven't been used for a while.
The fact that this section turned up in the first place implies it is safe to ignore, since it is auto-generated on need. If you already have it committed, and subsequently have it appear as removed on diff, open the Identity Inspector, drop-down the list of classes available under Custom Class, and see how the whole section exists once again.