SSWConsulting / SSWConsulting/SSW.Website
♻️ Fix CodeAuditor 🕵️♂️ 404 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 🕵️♂️ 404 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 🕵️♂️ 404 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 latest CodeAuditor scan linked in the issue and identify the site's 404 findings. Review related PRs marked CodeAuditor and the prior Sprint's screenshots and version history; done means fewer reported 404 errors, the version updated via the linked “Change x to y” rule, and the Sprint comment recorded.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html, nextjs
- Domain
- frontend, web-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100