Run build steps as a GitHub Action

[dotgrid]

I wondered if anyone has set up a GitHub Action to run the build steps?

I am imagining that my Aseprite files are stored in my Git repo, then when those change, GitHub Actions would run the cli tools to export/build the latest Atlas automatically.

(If this hasn't been set up before, I may try it on my next project. I'll be sure to share it with the community here.)

Thanks for a great tool!

[niedzielski]

Hi! Sounds cool!

I doubt anyone has set up a GitHub action with atlas-pack. For my own projects, which are tiny, I've just been building locally :] A CI build step would require a copy of Aseprite and I'm unsure on the licensing.

Regardless, I wish to share that the future of this project is uncertain. I split this library out a few years ago from a custom but unfinished game engine. As far as I can tell, no one but myself has ever used it! I'm still working on that engine and seem to make radical changes to it and this library a few times a year.

My current thinking is that this code is likely better as a reference than a library! There's just not much generically useful:

• Typing for Aseprite. I considered upstreaming this to DefinitelyTyped but the output is heavily dependent on the CLI parameters specified and I'm unsure how to account for that nicely. For the library, I just picked defaults that made sense for the spritesheet and wrapped the CLI with those expected params.
• A simple but opinionated animator utility. Animations are probably pretty core to most projects but this library makes the heavy assumption that only an atlas-pack conforming animation will be used. For example, the current animation duplicates cels to provide constant lookup time. This seems to work well for CPU performance in my games but wouldn't work well for many games which I would only guess at.
• Overall, the integration is probably a useful example but makes many other assumptions that likely would make it hard to use elsewhere.

I love the idea of folks using this project but, depending on requirements, the implementation to replace this library could be less than a few hundred lines.