Run something on linux + Mac -> uploads those as artifacts (those are not at publicly exposed URLs).
Make a release automatically named for the index of the workflow -- so these should be along the lines of number of master builds I believe. It will then upload the assets from the per-platform outputs and make a release.
Think it probably goes most of the way to what we need here.
cc @johnynek
As we discussed just breaking it into its own issue.
I was tooling about on a test repo as I mentioned earlier, setup some GitHub action flow there:
https://github.com/ianoc/bazel-scalafix
The release one now does:
Run something on linux + Mac -> uploads those as artifacts (those are not at publicly exposed URLs).
Make a release automatically named for the index of the workflow -- so these should be along the lines of number of master builds I believe. It will then upload the assets from the per-platform outputs and make a release.
Think it probably goes most of the way to what we need here.