celo-org / celo-org/celo-token-list
Github setup files
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 6
- Forks
- 15
- PR merge metrics
- No merged PRs in 30d
Description
### Tasks
- [ ] Issue and discussion templates ([like Foundry does](https://github.com/foundry-rs/foundry/issues/new/choose))
- [x] CODEOWNERS
- [ ] PR template
- [ ] CONTRIBUTING.md - optionally add how to contribute guide ([similar to what viem has](https://github.com/wevm/viem/blob/main/.github/CONTRIBUTING.md)) and link in README
- [x] SECURITY.md
- [ ] LICENSE
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.
Research direction
Review the linked Foundry issue and viem CONTRIBUTING.md example, then check which task-list items remain: issue and discussion templates, a PR template, CONTRIBUTING.md with a README link, and LICENSE. Done means those unchecked setup files are added and the task list is complete.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, markdown
- Domain
- devtools, documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100