Suggestion: Add Review process documentation
Open
- Dominant language
- TypeScript
- Stars
- 53
- Forks
- 63
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 15
Description
Often there’s variations of ways to do a review based on the PR submitted. For instance for docs you’ll just look at the delta.
For tests you run tests locally and for views you test a component directly.
Maybe it would be nice to write a small document that describes different types of review?
Contributor guide
Research direction
The issue does not name a file, test, or documentation entry point. First inspect the repository's existing contributor and review guidance, then define a small document covering review approaches for documentation changes, tests, and views; done means the guidance is added in an appropriate location and is clear enough for contributors to follow.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100