Complete repository health remediation#4
Merged
Conversation
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
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.
Summary
This closes the repository health audit by making the documented exporter commands work, removing third-party font requests, and adding checks for the browser code and tracked secrets.
Verification
python3 -m pytest tests/ -q(39 passed)python3 -m compileall -q bin scripts testspython3 scripts/check_frontend.py index.htmlnode tests/frontend.test.jspython3 scripts/scan_repo.py .Review notes
The exporter backfill uses Codex SQLite totals only when rollout usage for that thread is missing. Those records keep cost unknown because the database does not contain the per-call token breakdown needed for an accurate estimate.