chore: repo declutter — remove report/backup junk; plan shorter top-level#489
Merged
Conversation
- scanner-qa-report.html (root, generated, unreferenced) — also de-clutters the top-level listing so the README surfaces sooner. - specs/005-.../tasks.md.bak (editor backup) - specs/044-.../test-report.html (generated report)
Deploying mcpproxy-docs with
|
| Latest commit: |
ece20fb
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://bda6bfbc.mcpproxy-docs.pages.dev |
| Branch Preview URL: | https://chore-repo-declutter.mcpproxy-docs.pages.dev |
📦 Build ArtifactsWorkflow Run: View Run Available Artifacts
How to DownloadOption 1: GitHub Web UI (easiest)
Option 2: GitHub CLI gh run download 26265677199 --repo smart-mcp-proxy/mcpproxy-go
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Removes tracked junk and proposes how to shorten the GitHub top-level listing (so the README isn't pushed below the fold).
Deleted (this PR):
scanner-qa-report.html— generated report at repo root, referenced nowhere. Removing it also drops one entry from the top-level file listing.specs/005-rest-management-integration/tasks.md.bak— editor backup.specs/044-diagnostics-taxonomy/test-report.html— generated report.Why the top-level is long (and the realistic levers)
GitHub renders all top-level entries before the README. This repo has ~20 dirs + ~17 files; the dirs dominate and are mostly essential Go/source dirs.
Safe follow-ups (proposed, not in this PR):
SECURITY.md→.github/SECURITY.md— GitHub still detects it there for the community profile, and it leaves the root listing. It has no in-repo references. Deferred because PR chore: OSS repo hygiene — CoC, issue templates, dependabot, security policy #487 is currently editingSECURITY.mdand would conflict — best folded into chore: OSS repo hygiene — CoC, issue templates, dependabot, security policy #487's resolution.AUTOUPDATE.md: left at root — the Homebrew cask references it by path; moving risks breaking that link.Larger, riskier (separate effort):
test/+tests/into one dir (−1 top-level dir). Both contain Go packages and are wired into E2E scripts/CI (scripts/test-api-e2e.sh,run-oauth-e2e.sh,test-mcp.sh), so it needs path/import updates + a full E2E run.Also found (left for your call)
specs/043,046,050/execution_log.md— brainstorm work-logs; transient residue but they're spec history. Say the word and I'll delete them + add*.bak/execution_log.mdto.gitignoreto stop them recurring.