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

[ricochet]

I am in favor of breaking this out into individual repos, but would prefer that we use this repo to submodule them in to ease maintenance. I would like to take on this work. @rajatjindal and @alexcrichton - does that sound ok to you?

[rajatjindal]

Hi @ricochet,

Is this somehow related to #16? I am curious because if that is the case, we probably want to keep the "release machinery" separate from this actions repo. because IMO this repo serves as actions that helps setup/use bytecodealliance projects in any github workflow, which is different then reusable actions that helps with release process of bytecodealliance projects.

I still think beside GitHub actions workflow marketplace, we don't have lot of benefits of breaking down this repo into separate repos but I am also not strongly against it.

[ricochet]

My motivation is primarily to have de facto actions that are well maintained in the GitHub marketplace for the Wasm ecosystem. Specifically I have an immediate need for a setup-wasi-sdk and setup-wasm-tools for use outside of ba projects.

[alexcrichton]

I don't personally have any experience maintaining github actions, so I'd defer to others for preferences/commentary on this.

[rajatjindal]

My motivation is primarily to have de facto actions that are well maintained in the GitHub marketplace for the Wasm ecosystem.

I manage some GitHub actions, but none of them are in marketplace :). I have no concerns if we want to move this code to multiple repos to have them published in the marketplace 👍.

Specifically I have an immediate need for a setup-wasi-sdk and setup-wasm-tools for use outside of ba projects.

I mean you can use these actions outside of ba projects today (and we can quickly add wasi-sdk support if that is required and triggering the marketplace discussion.).