zaproxy / zaproxy/zaproxy-website
Review issue and pull request templates
Open
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 82
- Forks
- 132
- Avg merge
- 13h 14m
- Merged PRs (30d)
- 37
Description
Maybe to follow the wording used in other zaproxy repos.
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 the repository's issue and pull request templates, then compare their wording with templates in other ZAP repositories. Done means the templates have been reviewed and any needed wording updates are made; the issue names no template files or tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html
- Domain
- developer-experience
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100