I like to use Git submodules to share asset packs between projects. However, I’m always having to deal with changing IDs on the .import files whenever importing or updating these submodules into different projects. Is there a recommended way of handling this so I don’t have to keep re-importing these assets and committing changes to the .import files?
Is there a reason to not put .import in the .gitignore?
Why not let the engine decide the the .import should look like and generate it for every project that the assets go into?
append: Thinking more about it I understand that you would want specific import settings for the assets you use how do you use git submodules what kind of files do you share between projects?
If it’s relatively safe to add the .import file to my .gitignore, I may just do that. I don’t have a ton (yet) that I want to keep consistent between projects when it comes to import settings.
The files I’m sharing between projects that are the primary issue are images and 3D models. Again, if the only thing I’d lose by ignoring the .import file is unified import settings, that’s fine with me.
1 Like
Following up for anyone who stumbles upon this thread.
After trying adding “*.import” to the .gitignore in the subrepository, I realize now that this also means any time the parent repository is cloned to another machine the “.import” changes will not carry over. At this point I think it’s better to just not use git submodules at all. Instead these sorts of packages should be manually copied over and managed separately.
1 Like