Yicong-Huang opened a new pull request, #4714: URL: https://github.com/apache/texera/pull/4714
### What changes were proposed in this PR? Add a Codecov coverage badge to the existing `<p align="center">` stats block in `README.md`. The badge links to https://app.codecov.io/gh/apache/texera so reviewers / contributors can see the current overall coverage and click through to the per-flag breakdown without leaving the repo home page. ```diff <img alt="Static Badge" src="https://img.shields.io/badge/Largest_Deployment-100_nodes,_400_cores-green";> + <a href="https://app.codecov.io/gh/apache/texera";><img alt="Coverage" src="https://img.shields.io/codecov/c/github/apache/texera/main?logo=codecov&label=coverage";></a> </p> ``` Why now: PR #4666 wired `CODECOV_TOKEN` so push events on `main` and `release/**` now upload coverage. The latest few main commits at `https://codecov.io/api/v2/github/apache/repos/texera/branches/main` are reporting `46%` overall (frontend / scala / python / agent-service flags broken out). Without the badge, every "what's the current coverage?" question is a manual hop to the Codecov dashboard. Style note: shields.io to match the neighboring `Static Badge` images. Linked so a click jumps straight to the dashboard (the existing badges are images-only). ### Any related issues, documentation, discussions? Closes #4713. Related: #4666 (Phase 2 token wiring), #4645 (Phase 1 tokenless wiring). ### How was this PR tested? This is a one-line README change; rendered the new line in the GitHub markdown preview locally. The badge URL is already producing a non-`unknown` value (the dashboard returns `46%` for the latest main commits), so the rendered badge will be a real number on first view, not the placeholder. ### Was this PR authored or co-authored using generative AI tooling? Generated-by: Claude Code (Opus 4.7, 1M context) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
