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
As Gamutoware is made to be worked on on faculty computers, size is an important concern, especially since memory requirements increase along with minigame count. As Gamutoware is very modular, with each minigame being its own folder, it's easy for people to work on their projects without having access to all other ones. How can we change the contribution workflow to allow for that?
The text was updated successfully, but these errors were encountered:
Using partial clones would be a good start to reduce unnecessary downloads of file.
By using a blobless clone we can reduce the size from 357M to just 149M.
A possible command would be: git clone --filter=blob:none [email protected]:moraguma/GamutoWare.git More info on partial clones
@Gvinfinity that would be a good start, but I think a more definitive solution would need to allow cloning the repo without downloading every single minigame. The idea is that, while the core should always be fairly small, new minigames will keep being added as long as Gamutoware exists. I think an ideal solution would be for people to be able to clone the repo with only the inclusion of the current year's and the demo's minigame packs
Either way, we should go for blobless clones for the class next year
As Gamutoware is made to be worked on on faculty computers, size is an important concern, especially since memory requirements increase along with minigame count. As Gamutoware is very modular, with each minigame being its own folder, it's easy for people to work on their projects without having access to all other ones. How can we change the contribution workflow to allow for that?
The text was updated successfully, but these errors were encountered: