Skip to content

chore: Remove 5 garbage 404 JSON files from repo root - #6

Merged
amafjarkasi merged 2 commits into
masterfrom
chore/remove-404-garbage-json
Jul 31, 2026
Merged

amafjarkasi merged 2 commits into
masterfrom
chore/remove-404-garbage-json

Conversation

@amafjarkasi

Copy link
Copy Markdown
Owner

Cleanup. cloudflare.json, cloudflare2.json, cloudflare3.json, datadog.json, and sentry.json were 14-byte 404: Not Found error bodies — failed OpenAPI spec downloads that got committed to the repo root by accident (likely a specforge fetch that 404'd and saved the error response).

Unreferenced anywhere in source/docs/tests. Safe deletion.

The other JSON files in the tree are all legitimate: assets/ (IR schema + marketplace indexes), fixtures/external/ (real test specs), generated SDK specforge-version.json/package.json, docs-site config, and the VS Code extension. The docs-site/.docusaurus/ cache JSON is gitignored (not tracked).

cloudflare.json, cloudflare2.json, cloudflare3.json, datadog.json, and
sentry.json were 14-byte '404: Not Found' error bodies — failed spec
downloads that got committed to the repo root by accident. Unreferenced
anywhere in source. Removed.
@gemini-code-assist

Copy link
Copy Markdown

Caution

The consumer version of Gemini Code Assist on GitHub has been sunset. All code review activity has officially ceased.

@qodo-code-review

Copy link
Copy Markdown

PR Summary by Qodo

Remove accidentally committed 404 JSON error bodies from repo root

✨ Enhancement 🕐 Less than 5 minutes

Grey Divider

AI Description

• Delete five root-level JSON files that only contained 404: Not Found error bodies.
• Remove unreferenced, accidental artifacts likely produced by a failed OpenAPI/spec fetch.
• Reduce repo clutter and prevent confusion with legitimate JSON assets elsewhere.
High-Level Assessment

Deleting these unreferenced, invalid JSON artifacts is the correct approach; alternatives (e.g., moving them to fixtures or keeping for debugging) would only add noise since the contents are just a 404 error body.

@qodo-code-review

Copy link
Copy Markdown

Code Review by Qodo

🐞 Bugs (0) 📘 Rule violations (0) 📎 Requirement gaps (0)

Grey Divider

Great, no issues found!

Qodo reviewed your code and found no material issues that require review

Grey Divider

To customize comments, go to the Qodo configuration screen, or learn more in the docs.

Qodo Logo

The 5 removed 404 JSON files got committed because a failed spec download
wrote an error body to the repo root and it got 'git add'ed. Add /*.json
to .gitignore so any future stray root JSON is ignored automatically.
Safe: zero root-level JSON is tracked, and subdir JSON (assets/,
fixtures/, examples/, docs-site/, vscode-extension/) is unaffected.
action.yml (YAML) stays tracked.
@amafjarkasi
amafjarkasi merged commit 1806696 into master Jul 31, 2026
4 of 5 checks passed
@amafjarkasi
amafjarkasi deleted the chore/remove-404-garbage-json branch July 31, 2026 03:51
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.

1 participant