bytecodealliance / bytecodealliance/go-modules
Go module paths tracking issue
Open
@ricochet is already working on this.
Since Nov 5, 2024.
- Dominant language
- Go
- Stars
- 148
- Forks
- 20
- PR merge metrics
- No merged PRs in 30d
Description
- POC go.bytecodealliance.org with duplicate repo at https://github.com/bytecodealliance/go-modules
- Disable GitHub Pages on https://github.com/bytecodealliance/go-modules repo (@ydnar)
- Delete or rename POC https://github.com/bytecodealliance/go-modules repo (@ydnar)
- Set up CNAME for go.bytecodealliance.org → bytecodealliance.github.io (@ricochet)
- Rename https://github.com/bytecodealliance/wasm-tools-go → https://github.com/bytecodealliance/go-modules (@ydnar)
- Fork https://github.com/bytecodealliance/go-modules → https://github.com/bytecodealliance/wasm-tools-go (@ydnar)
- Mass find & replace
github.com/bytecodealliance/wasm-tools-go→go.bytecodealliance.orgin https://github.com/bytecodealliance/go-modules repo (@lxfontes) - Enable GitHub pages on https://github.com/bytecodealliance/go-modules repo @
go.bytecodealliance.org(@lxfontes) - Fix links in Releases: https://github.com/bytecodealliance/go-modules/releases (@ydnar)
- Deprecate the github.com/bytecodealliance/wasm-tools-go module (@ydnar)
- Blog post? (@lxfontes + @ricochet?)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.