OurTechCommunity / OurTechCommunity/catchup
Add PR checklist.
Open
Nobody has claimed this yet.
documentation
- Dominant language
- JavaScript
- Stars
- 19
- Forks
- 18
- Avg merge
- 3d 6h
- Merged PRs (30d)
- 3
Description
Add PR checklist primarily to remind people to run Prettier before opening a PR.
Credits: @KartikSoneji
PS: Which label should one apply to such an issue? Do we need a new label? If yes, what would it be called?
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
Locate the repository's pull-request template or contribution guidance; the issue does not name a specific file. Read the existing contributor instructions, then add a PR checklist that reminds contributors to run Prettier before opening a pull request. Done means the checklist is visible to contributors when they create a PR.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- developer-experience, documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100