Replies: 2 comments 1 reply
-
That’s a good idea. I’ve setup actions to build & upload artifacts before. One thing that’s maybe not very user-friendly though is that to download the built fonts you have to know to click the little green checkmark icon next to a commit and then find download links at the end-ish of that page. It’s possible to create releases, but those require tagging and would cause one tag for every commit. Maybe it’s possible to create comments on a commit with the download links (automatically in the action) |
Beta Was this translation helpful? Give feedback.
-
Done. |
Beta Was this translation helpful? Give feedback.
-
Github Actions is well suited to the kind of compilation tasks which is needed to build font files and releases, and it can also handle publishing the releases automatically with semantic versioning.
Using Github Actions would free up valuable processing power/time from the developer's systems, and relieves the mental load as well; the developers need not have to juggle around managing the built font files, then uploading them to Github releases, then tagging them properly.
It's easy to set up and free, it's just a matter of configuring the build workflow, and having it output the artifacts needed. It could also allow for creating separate archives, like an archive just for Inter Text, an archive for Inter Display, etc.
Beta Was this translation helpful? Give feedback.
All reactions