open-feature / open-feature/flagd
[DOC] Expand the contributing documentation
Open
Nobody has claimed this yet.
documentation
- Dominant language
- Go
- Stars
- 997
- Forks
- 136
- Avg merge
- 4d 8h
- Merged PRs (30d)
- 11
Description
Change in the documentation
Expand the contributing documentation to include information on the tech stack, testing, PR, and release process. The JS SDK contributing doc can be used as a reference.
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
Start by locating flagd’s current contributing documentation and compare it with the referenced JS SDK CONTRIBUTING.md. Add information covering the tech stack, testing, pull requests, and release process; done means each requested topic is documented and the contribution guide is complete and easy to follow.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100