enhancement: option to upload artifact on ci workflow

[Ludea]

For now I use https://github.com/actions/upload-artifact to do the job.

It can be usefull to add an option to do the same thing.

WDYT ?

[FabianLars]

Since this is probablyyy a niche feature, i think i'd prefer if the action would output the paths of the generated bundles instead. This would be way more flexible and could cover more use cases. any thoughts about that?

[Ludea]

it's an alternative solution, why not

[Ludea]

I reopen, because after some thoughts, I would like to add short commit into assets name, to avoid confusion with release assets

[septum]

This is slightly related, but seems like a good place to ask this: Do the artifacts stick around after the action ends? I ask this because we are having trouble sending them to an S3 bucket, with the error output stating that the path does not exist.

[FabianLars]

Yes they do, but only for the following steps of the current jobs, other jobs won't have access to it. Also, the action will return the paths of the artifacts as a json string which you may be able to use (though if you know your project the paths are pretty easy to predict).

[martpie]

I would like to second the ability to upload artifacts without having to rely on releases. I very frequently build all binaries as part of a PR, and it is really nice to be able to go to a run artifacts section and download binaries from there (for testers, etc).

Example: https://github.com/martpie/museeks/actions/runs/8484717113