Skip to content

[repo-health] README: No live CI status badge — build health is invisible to contributors #15

@Liohtml

Description

@Liohtml

Summary

The README has a hardcoded static test badge but no live GitHub Actions CI badge. Contributors and users cannot see the current build/test status at a glance, and the repo gives the impression of no active CI even though a CI workflow exists.

Category

README

Severity

Low

Location

  • File: README.md
  • Line(s): 7–10 (badge block at the top)

Details

The current badge block:

[![Rust](https://img.shields.io/badge/Rust-1.75%2B-orange?logo=rust)](https://www.rust-lang.org/)
[![License: MIT](https://img.shields.io/badge/License-MIT-blue.svg)](LICENSE-MIT)
[![License: Apache 2.0](https://img.shields.io/badge/License-Apache%202.0-blue.svg)](LICENSE-APACHE)
[![Tests](https://img.shields.io/badge/tests-175%20passing-brightgreen)]()

The repo has a working CI pipeline at .github/workflows/ci.yml that runs tests, Clippy, and rustfmt on push and PR, but there is no badge linking to it. As a result:

  1. Visitors cannot see whether the latest commit builds/passes tests.
  2. The existing static Tests badge (issue [repo-health] Low: Static test count badge is stale (shows 175, codebase has 269 tests) and has a broken link #13) is the only signal — but it is stale and non-clickable.
  3. New contributors cannot confirm the project is in a healthy state before opening a PR.

Suggested Fix

Add a GitHub Actions CI badge immediately after the existing badges:

[![CI](https://github.com/Liohtml/RUSTScrapling/actions/workflows/ci.yml/badge.svg)](https://github.com/Liohtml/RUSTScrapling/actions/workflows/ci.yml)

Optionally also replace the static test badge (see issue #13) with this single dynamic badge, which covers pass/fail for the full test suite.

Effort Estimate

5 min


Automated finding by repo-health-agent v1.0

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions