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
We need to decide if we are prioritising fonts built locally (and uploaded into, and onboarded from, the repo) or fonts built remotely and packaged using GHA. I have a strong preference for GHA, but we have been ambivalent on this point.
A lot of designers are still not empowered with GHA and tag releases. Also some projects don't fit the template and would need to customise the action (which can be complicated in some cases). To make sure the template can allow these different scenarios, I would allow what we instruct people to do: having the font folder in their repo.
For the hundreds of fonts that we have onbaorded; using github is already a complicated step for designers, asking them to use github action simply results in not working on github anymore.
A user wrote me
I guess
.gitignore
should be updated to remove that line.... thoughts @simoncozens ?The text was updated successfully, but these errors were encountered: