Consider adopting a simple GitHub Action workflow

[EnnuiL]

I believe that it would be ideal to adopt a quite simple GH Action workflow that automatically uploads its artifacts for testing purposes;
The question is: how exactly should it be done? I fear that the approach adopted by Fabric Example Mod might be a bit too complex, so I was thinking of adopting Boring Template's workflow as the template workflow, although with it being commented so it's more modification-friendly.
Suggestion are welcome! i desperately need them

[Oliver-makes-code]

It'd be nice to have Gradle cache enabled for workflows, like in Create Fabric's workflow build

[EnnuiL]

It'd be nice to have Gradle cache enabled for workflows, like in Create Fabric's workflow build

This seems like an interesting idea; My only main concern is the apparent lack of control over the cache, 'cause yeah, who hasn't nuked the Gradle cache once in a while? This should be something to be investigated

[BurAndBY]

I'm using this. Can make a PR if needed.

[BurAndBY]

I'm using this. Can make a PR if needed.

Takes some time, but does it's job.

[EnnuiL]

After some thinking, now I'm leaning towards a pretty simple CI workflow, with no caching or anything that requires user intervention; I'd rather teach the user about how to work on more complex CIs than dumping one on their plates without explaining how it works