docs(docs): add tech-stack badges to README (shields.io for-the-badge) (#273)#274
Conversation
#273) Add 31 shields.io for-the-badge style badges to the README, grouped into a 4-badge status row (License · Release · CI · Python) and four tech-stack rows (Backend, Frontend, ML/AI, Tooling). Matches the visual style of the user-provided HTML5 badge example. All shields URLs HEAD-probed (200) and SVG-verified for logo presence on every badge that cites one (FastAPI, Pydantic, SQLAlchemy, PostgreSQL, React, TypeScript, Vite, Tailwind, shadcn/ui, TanStack Query, scikit-learn, PydanticAI, OpenAI, Anthropic, Ollama, Docker, uv, pnpm, GitHub Actions, Ruff, pytest, Python). LightGBM, XGBoost, structlog, mypy, and Alembic render as text-only badges by design — no canonical simple-icons brand entries exist for them. Release + CI badges are dynamic: they read from this repo so they self-update with each release and CI run on `dev` without further edits.
There was a problem hiding this comment.
Sorry @w7-mgfcode, you have reached your weekly rate limit of 500000 diff characters.
Please try again later or upgrade to continue using Sourcery
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Closes #273.
Summary
Adds a 31-badge block to the README between the tagline and the Features section, matching the user-provided HTML5 `for-the-badge` style. One status row + four tech-stack rows (Backend / Frontend / ML/AI / Tooling). No new files, no new assets — every badge resolves through shields.io.
Layout
Validation
Why this PR doesn't risk drift
The Release + CI badges are dynamic — they read from this repo. They self-update with every release and CI run on `dev` without any further edits to the README.
Test plan