Add `merkle` and `formats` repo to readme
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 45/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Stale
- Domain
- documentation
Research direction
Locate the repository README referenced by the issue and review how other repositories are listed. Add merkle and, if confirmed as in scope, formats, then verify both entries appear consistently with the surrounding README content.
Written by the indexing model from the issue text.
Description
I think it's worth adding `merkle` and possibly `formats` here too as they're pretty central to everything transparency.dev is about.
Originally posted by @AlCutter in https://github.com/transparency-dev/.github/pull/3#discussion_r1872991243
- Dominant language
- No language data
- Stars
- 2
- Forks
- 7
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
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.
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
palladius/rails8-app-on-gcp#145 ·
-
NeedsTriage
Difficulty 1/5 Under an hour Newbie friendliness 90/100
-
error Open
Difficulty 1/5 Under an hour Newbie friendliness 85/100
-
Difficulty 1/5 Under an hour Newbie friendliness 85/100
-
textual definition
Difficulty 1/5 Under an hour Newbie friendliness 90/100
geneontology/go-ontology#32653 ·