Skip to content

Add: Refactor requirements doc - #383

Open
suspect15 wants to merge 11 commits into
RetroAchievements:mainfrom
suspect15:refactor-reqs
Open

Add: Refactor requirements doc#383
suspect15 wants to merge 11 commits into
RetroAchievements:mainfrom
suspect15:refactor-reqs

Conversation

@suspect15

Copy link
Copy Markdown
Contributor

Adds a requirements doc for refactored inactive developer sets. The purpose of this is to establish a standard for bringing substandard, inactive developer sets up to current quality standards to ensure long term stability and easiest possible future maintenance.

@suspect15
suspect15 marked this pull request as draft June 15, 2026 11:44
Comment thread docs/guidelines/content/refactor-requirements.md Outdated
@suspect15
suspect15 marked this pull request as ready for review September 6, 2026 01:27
@greptile-apps

greptile-apps Bot commented Sep 6, 2026

Copy link
Copy Markdown
Contributor

Greptile Summary

Adds refactoring requirements and English sidebar navigation.

  • Defines standards for code notes, logic, writing, and Rich Presence.
  • Removes premature save-state submission guidance.

Confidence Score: 5/5

The PR appears safe to merge.

No actionable new issues remain. The missing save-state instructions were removed. suspect15 accepted the deliberate heading hierarchy as appropriate.

Reviews (2): Last reviewed commit: "removed save repo verbiage" | Re-trigger Greptile

Comment thread docs/guidelines/content/refactor-requirements.md
Comment thread docs/guidelines/content/refactor-requirements.md
Comment thread docs/guidelines/content/refactor-requirements.md Outdated
Comment thread docs/.vitepress/config/es.ts Outdated
Comment thread docs/guidelines/content/refactor-requirements.md
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants