SSWConsulting / SSWConsulting/SSW.Website
♻️ Fix CodeAuditor 🚨 errors
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 14
- Forks
- 10
- Avg merge
- 13h 51m
- Merged PRs (30d)
- 38
Description
Version 0
Cc: @bradystroud @adamcogan @tombui99
Hi Team,
This is a long lasting PBI item to ensure every Sprint some time is spent working on reducing the amount of 🚨 errors CodeAuditor is finding.
The latest scan can be found here: https://codeauditor.com/latest/02ad5e57-04e6-4c4f-bdd4-1e62d495e6d5/ssw.com.au%2Frules
Tasks
- Work on reducing the 🚨 errors every Sprint
- Increment the version number each Sprint using the "Change x to y" rule (https://www.ssw.com.au/rules/change-from-x-to-y/) (this is to track history)
- Comment on the PBI every Sprint with the following information:
- The PRs that were made in relation to fixing CodeAuditor errors (each PR fixing CodeAuditor issues should be marked with the "CodeAuditor" tag)
- The diff from last Sprint (screenshots)
Thanks!
< As per https://ssw.com.au/rules/managing-errors-with-code-auditor/ >
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
Start with the linked latest CodeAuditor scan and review the repository's current errors; the issue does not name specific files or tests. Done means reducing the reported errors, incrementing the version using the linked “Change x to y” rule, and commenting with related CodeAuditor PRs and the Sprint diff screenshots.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nextjs
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100