Document relationship to `componentize-go`

Open
#428 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
48/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Quiet
Tech stack
go
Domain
documentation

Research direction

Start with the repository README and review how this project relates to componentize-go. Clarify whether the repository should be archived and document the relationship in the README; done means the status and relationship are clearly explained.

Written by the indexing model from the issue text.

Description

Seems like this repo is deprecated. Should it be archived? I think it at least deserves a note in the read-me explaining the relationship between this and componentize-go.

Dominant language
Go
Stars
148
Forks
20
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from bytecodealliance/go-modules

All issues in bytecodealliance/go-modules

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.