You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently there is an issue with using submodules that points at subprojects kept as a branches in the islet-asset repository.
The main repository takes about 83GB disk space, it’s because git duplicates the islet-asset repo for each submodule.
This is also the reason why the initialization process (./scripts/init.sh) takes a lot of time. I think that if we’re going to make the project more user friendly for potential open source contributors, this should be fixed somehow. The easiest way seems to be keeping these subprojects as separate git repositories. But, I’m not a git/GitHub guru on that matter, and maybe there is a better solution.
The text was updated successfully, but these errors were encountered:
Good to report this issue with the visualization! I also agree that this huge disk consumption issue should be resolved.
We've avoided this issue by using only a minimum dependency on ci (e.g., using init_sh_min.sh instead of init.sh), yet another solution seems to be needed.
One quick solution would be maintaining another script equivalent to init.sh which does not include git history in third-party modules. With the script, the disk consumption would be reduced to around 21GB (still huge) while all third-party modules are available like the below.
Currently there is an issue with using submodules that points at subprojects kept as a branches in the islet-asset repository.
The main repository takes about 83GB disk space, it’s because git duplicates the islet-asset repo for each submodule.
This is also the reason why the initialization process (./scripts/init.sh) takes a lot of time. I think that if we’re going to make the project more user friendly for potential open source contributors, this should be fixed somehow. The easiest way seems to be keeping these subprojects as separate git repositories. But, I’m not a git/GitHub guru on that matter, and maybe there is a better solution.
The text was updated successfully, but these errors were encountered: