koobas.hobune.stream
m_PrefabInternal, m_PrefabInstance & m_PrefabAsset vs Source Control
Hello! I think we are not the only ones running into this but I could not find an answer anywhere online.
Pretty often when working on our Unity project, asset files seem to change their values for "m_PrefabInternal", "m_PrefabInstance" and "m_PrefabAsset" for no discernible reason. For example: 
This is causing a lot of merging work and grief. So our questions are:
Does anyone know what this is caused by?
Can we discard these changes when committing and otherwise ignore these? If not what are the consequences, and how can we work around this?
If anyone has any information I think it will be very welcome not just by us but many people who are running into this!
This looks like the consequences of a Unity version update. The new fields are those used by the new prefab system. We had a lot of changes that looked like this when we upgraded to 2018.3, and just checked them in to source control. It wasn't a problem. So... why can't you do that? How is it causing you grief?
@Bonfire-Boy This is really good to know! The grief is caused by a lot of file differences that have unknown effects. The last we need on a large project is starting to get unexplained failures due to some internal IDs changing. $$anonymous$$oving forward blindly and "hoping for the best" would be a recipe for disaster. $$anonymous$$nowing these are transparent is great, and the whole $$anonymous$$m can move forward without wondering if we are setting ourselves up for incompatibilities or corruption.
I think this could perhaps occur because different members of your team are using different versions of Unity. The syntax of .prefab and .unity YAML files has changed between Unity versions.
