SSWConsulting / SSWConsulting/SSW.Rules.Content
SSW.Rules - Why having "legacy" instead of archiving them?
Open
Nobody has claimed this yet.
- Dominant language
- MDX
- Stars
- 62
- Forks
- 196
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 112
Description
Cc: @bradystroud @adamcogan
Hi Team
https://www.ssw.com.au/rules/rules-to-better-code-legacy/
This rule category seems out of place - it's legacy - ... we should archive it
- 1. Please confirm with the Product Owner
- 2. Action archiving the category and its rules
Rules to Better Code (legacy) - 3 Rules
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
Review the linked “Rules to Better Code (legacy)” category and its three listed rules first. Confirm the archival decision with the Product Owner, then archive the category and its rules and verify that the legacy category is no longer presented.
Written by the indexing model from the issue text.
Assessment
- Domain
- content, documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100