MozillaSecurity / MozillaSecurity/attackanddefense.dev
Discussion
Open
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 2
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
We don't want comments, but we should provide a pointer to our matrix chat
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.
Research direction
No file or test is named. Start by locating the blog's discussion or contact entry points, then add a pointer to the project's Matrix chat and confirm that visitors have a clear alternative to comments.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100