Split into multiple GitHub Actions repositories

[jcbhmr]

Why? This lets you get listed on the GitHub Actions marketplace: https://github.com/marketplace?category=&type=actions&verification=&query=wasmtime https://github.com/marketplace?category=&type=actions&verification=&query=wasm-tools

I would like to transfer these two repositories into the @bytecodealliance organization to make them "official": https://github.com/jcbhmr/setup-wasm-tools https://github.com/jcbhmr/setup-wasmtime . I'm not sure how to do that or if @bytecodealliance is open to that. 🤷‍♀️

[rajatjindal]

Hi @jcbhmr,

Disclaimer: I am a new contributor to bytecodealliance, and this actions repo is my first contribution here. Therefore, I wanted to clarify that I am speaking for myself here (and not on behalf of bytecodealliance).

Besides the discoverability in the marketplace, is there any other benefit of splitting the action into multiple repos? Given the simplicity of these actions today, I would prefer to keep them in the same repo unless we have a more compelling reason to split them.

Thanks Rajat Jindal

[jcbhmr]

Not really, no. All the benefits and drawbacks of polyrepo vs monorepo still apply (tagging/release management, etc).

I wouldn't discount the discoverability benefits of being listed on the GitHub Actions Marketplace though. 🤷‍♀️

[rajatjindal]

The first result of "github actions wasmtime" on Google search is this repo. With that in mind, I will not be too worried about listing in the Github actions marketplace but will defer the decision to someone with more authority in the bytecodealliance org.

[jcbhmr]

building on this idea: i would like to transfer these to @bytecodealliance too: https://github.com/jcbhmr/setup-javy https://github.com/jcbhmr/setup-wit-bindgen https://github.com/jcbhmr/setup-cargo-component