Hey, just a quick question that nobody answered on IRC and I couldn’t find documentation on elsewhere.
When developing Sponge and preparing for a pull request, what’s the standard workflow for handling the submodules with Git? I realise for me to test compilation and use my implementation I must have my updated version of the API/Common to compile SpongeForge/SpongeVanilla, however if I change the .gitmodules file to point to my fork of the API/Common then when I make a pull request it will include those changes. If I revert them back to the original submodules but change the branch to my feature/(name) when making a pull request it will not compile via travis unless the API changes are pulled first, etc.
It can get quite messy thinking about it and I’ve not found much to go on. If anyone who’s already developed for Sponge or a Sponge developer could give a standard process, it would be nice. I understand many people will take this as obvious but submodules for me are a new area; I’ve never really had a project depend on them.
Thanks for the time, if you attempt to answer this, anyway!