There are files included in the package that is exported from aem that aren't needed for the storybook library. If these files are to be included, they will overwrite the user's local aem, with potentially unexpected and harmful results. We should find a way to only include the files that are pertinent to the storybook library, and exclude the parent files, as those files could be different on each person's local instance.
After some testing, we found that gitignore-ing the folder level .content.xml files for the ancestor folders of the storybook content library is an effective solution
There are files included in the package that is exported from aem that aren't needed for the storybook library. If these files are to be included, they will overwrite the user's local aem, with potentially unexpected and harmful results. We should find a way to only include the files that are pertinent to the storybook library, and exclude the parent files, as those files could be different on each person's local instance.