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
In making Transmutor, I noticed there was a standalone repo here on roboDocs for MutatorScale, and a copy of it in this repo... almost. I noticed they diverged only slightly, so I made roboDocs/MutatorScale#4 to update it.
Going forward, I think we should update this repo to use a submodule of MutatorScale, instead of just copying it, like I do on Transmutor.
It works fairly seamlessly except for a few things, the primary thing is that when you clone a repo, by default the submodules aren't cloned as well, you need to add either another argument to your pull or run an extra command, see working with submodules.
Because of this, you need to package things up more neatly for Mechanic and point it to a zip instead of just the repo. I have example of how it's done in a github action. Then you just point it to the latest release
It's a little extra work but I think it would benefit us in the future because there isn't a risk of the different versions of the library diverging further. If you are interested I will make a PR.
The text was updated successfully, but these errors were encountered:
I guess the auto zip download was the reason why that packages was embedded in the ScaleFast. I was unaware of your setup! super neat: action -> release -> downloadable zip url
But before making it more complex: is mutatorScale used outside of ScaleFast?
@typemytype I use it in Transmutor and occasional scripts for making things like tabular figures or monospacing a typeface, so let's count that as 1 and a half uses outside ScaleFast :)
Hi all (@typemytype, @roberto-arista),
In making Transmutor, I noticed there was a standalone repo here on roboDocs for MutatorScale, and a copy of it in this repo... almost. I noticed they diverged only slightly, so I made roboDocs/MutatorScale#4 to update it.
Going forward, I think we should update this repo to use a submodule of MutatorScale, instead of just copying it, like I do on Transmutor.
It works fairly seamlessly except for a few things, the primary thing is that when you clone a repo, by default the submodules aren't cloned as well, you need to add either another argument to your pull or run an extra command, see working with submodules.
Because of this, you need to package things up more neatly for Mechanic and point it to a zip instead of just the repo. I have example of how it's done in a github action. Then you just point it to the latest release
It's a little extra work but I think it would benefit us in the future because there isn't a risk of the different versions of the library diverging further. If you are interested I will make a PR.
The text was updated successfully, but these errors were encountered: