Skip to content

docs(readme): add AI slop inside + downloads badges - #550

Merged
KooshaPari merged 1 commit into
mainfrom
add-badges-2026-08-31
Sep 1, 2026
Merged

docs(readme): add AI slop inside + downloads badges#550
KooshaPari merged 1 commit into
mainfrom
add-badges-2026-08-31

Conversation

@KooshaPari

@KooshaPari KooshaPari commented Sep 1, 2026

Copy link
Copy Markdown
Owner

User description

Automated PR: add 2 badges to README.

  • AI slop inside (self-declaration)
  • GitHub downloads counter (shields.io)

CodeAnt-AI Description

Add AI disclosure and download count badges to the README

What Changed

  • The README now displays an “AI slop inside” disclosure badge linking to sladge.net
  • The README now displays a GitHub downloads badge linking to the project’s releases

Impact

✅ Visible AI-use disclosure
✅ At-a-glance download counts
✅ Direct access to project releases

💡 Usage Guide

Checking Your Pull Request

Every time you make a pull request, our system automatically looks through it. We check for security issues, mistakes in how you're setting up your infrastructure, and common code problems. We do this to make sure your changes are solid and won't cause any trouble later.

Talking to CodeAnt AI

Got a question or need a hand with something in your pull request? You can easily get in touch with CodeAnt AI right here. Just type the following in a comment on your pull request, and replace "Your question here" with whatever you want to ask:

@codeant-ai ask: Your question here

This lets you have a chat with CodeAnt AI about your pull request, making it easier to understand and improve your code.

Example

@codeant-ai ask: Can you suggest a safer alternative to storing this secret?

Preserve Org Learnings with CodeAnt

You can record team preferences so CodeAnt AI applies them in future reviews. Reply directly to the specific CodeAnt AI suggestion (in the same thread) and replace "Your feedback here" with your input:

@codeant-ai: Your feedback here

This helps CodeAnt AI learn and adapt to your team's coding style and standards.

Example

@codeant-ai: Do not flag unused imports.

Retrigger review

Ask CodeAnt AI to review the PR again, by typing:

@codeant-ai: review

Check Your Repository Health

To analyze the health of your code repository, visit our dashboard at https://app.codeant.ai. This tool helps you identify potential issues and areas for improvement in your codebase, ensuring your repository maintains high standards of code health.

Copilot AI lite review requested due to automatic review settings September 1, 2026 04:24

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

@codeant-ai

codeant-ai Bot commented Sep 1, 2026

Copy link
Copy Markdown

🤖 CodeAnt AI — Review Status

Status Commit Started (UTC) Finished (UTC)
✅ Reviewed your PR 64bdcea Sep 01, 2026 · 04:24 04:25

@codeant-ai

codeant-ai Bot commented Sep 1, 2026

Copy link
Copy Markdown

Thanks for using CodeAnt! 🎉

We're free for open-source projects. if you're enjoying it, help us grow by sharing.

Share on X ·
Reddit ·
LinkedIn

@coderabbitai

coderabbitai Bot commented Sep 1, 2026

Copy link
Copy Markdown

Review Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Team

Run ID: 721301d9-55e6-4eb4-9f87-b09e72ab92ad

📥 Commits

Reviewing files that changed from the base of the PR and between fe230fa and 64bdcea.

📒 Files selected for processing (1)
  • README.md

Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review.

📜 Recent review details
⏰ Context from checks skipped due to timeout. (96)
  • GitHub Check: semgrep-cloud-platform/scan
  • GitHub Check: CVE feed subscription smoke (soft)
  • GitHub Check: SLSA protected-environment SelfCheck
  • GitHub Check: cargo deny check
  • GitHub Check: Socket posture SelfCheck
  • GitHub Check: miri permutation · SelfCheck
  • GitHub Check: SBOM policy SelfCheck
  • GitHub Check: cargo audit
  • GitHub Check: env.example hygiene
  • GitHub Check: sl-daemon · repository builder image offline build / sl-daemon · repository builder image offline build
  • GitHub Check: gitleaks
  • GitHub Check: PII redaction helper smoke (soft)
  • GitHub Check: sl-daemon · locked offline build
  • GitHub Check: rootless-only matrix scaffold
  • GitHub Check: release · SOURCE_DATE_EPOCH policy
  • GitHub Check: trufflehog
  • GitHub Check: cargo-fetch no-net policy
  • GitHub Check: miri permutation · race_model
  • GitHub Check: hermetic · SLSA isolation checklist (soft)
  • GitHub Check: hermetic · reusable workflow provenance (soft)
  • GitHub Check: token-burn ledger smoke (soft)
  • GitHub Check: daemon graph hard · tokio graph
  • GitHub Check: daemon graph hard · SelfCheck
  • GitHub Check: loom permutation · daemon pipeline
  • GitHub Check: soft loom · SelfCheck
  • GitHub Check: hermetic · exact rustc toolchain pin (soft)
  • GitHub Check: loom permutation · daemon broadcast
  • GitHub Check: soft loom · daemon mpsc
  • GitHub Check: compression ratio gate
  • GitHub Check: cross-language parity SelfCheck
  • GitHub Check: sandbox boundary smoke
  • GitHub Check: loom permutation · SelfCheck
  • GitHub Check: loom permutation · hermetic wrappers
  • GitHub Check: loom permutation · daemon shutdown
  • GitHub Check: session-ledger build · macos-latest
  • GitHub Check: exotic check · x86_64-unknown-linux-musl
  • GitHub Check: soft loom · loom_model core
  • GitHub Check: update check hard · SelfCheck
  • GitHub Check: loom permutation · core models
  • GitHub Check: sl-viewer help · unit tests
  • GitHub Check: update check hard · sl-daemon tests
  • GitHub Check: sl-daemon build · windows-latest
  • GitHub Check: session-ledger build · ubuntu-latest
  • GitHub Check: latency baseline check
  • GitHub Check: soft loom · daemon broadcast
  • GitHub Check: sl-daemon build · macos-latest
  • GitHub Check: exotic check · aarch64-unknown-linux-gnu
  • GitHub Check: sl-daemon build · ubuntu-latest
  • GitHub Check: loom permutation · daemon mpsc
  • GitHub Check: update check hard · root SelfCheck wrapper
  • GitHub Check: pipeline perf regression gate
  • GitHub Check: sl-viewer help · SelfCheck
  • GitHub Check: sl-viewer macOS app · artifact
  • GitHub Check: shuttle permutation · SelfCheck
  • GitHub Check: browser e2e · axe · responsive · visual
  • GitHub Check: tsan permutation · SelfCheck
  • GitHub Check: Lint & Format
  • GitHub Check: envelope-crypto · SelfCheck
  • GitHub Check: scorecard
  • GitHub Check: Detect Languages
  • GitHub Check: Pull secrets from Infisical
  • GitHub Check: rootless-only matrix policy
  • GitHub Check: tsan permutation · race_model
  • GitHub Check: rootless-only matrix · SelfCheck
  • GitHub Check: shuttle permutation · cargo test shuttle_permutation
  • GitHub Check: Platform Signing Readiness (signing-hard.yml gate)
  • GitHub Check: alloc profile hard · dhat smoke
  • GitHub Check: prepare
  • GitHub Check: Eval Reproducibility SelfCheck
  • GitHub Check: jemalloc default-on · unix default build
  • GitHub Check: jemalloc default-on · SelfCheck
  • GitHub Check: Dependency Review
  • GitHub Check: soft fuzz · SelfCheck
  • GitHub Check: ci / rootless-nonet policy smoke
  • GitHub Check: alloc profile hard · SelfCheck
  • GitHub Check: fuzz blocking · SelfCheck
  • GitHub Check: jemalloc hard · SelfCheck
  • GitHub Check: load macro gate · SelfCheck
  • GitHub Check: signing hard · SelfCheck
  • GitHub Check: jemalloc default-on · windows default build
  • GitHub Check: soft shuttle · SelfCheck
  • GitHub Check: jemalloc hard · feature build
  • GitHub Check: load macro gate · macro routes smoke
  • GitHub Check: score
  • GitHub Check: fuzz blocking · sustained 30s
  • GitHub Check: soft update check · SelfCheck
  • GitHub Check: rootless/no-net · SelfCheck
  • GitHub Check: visual contract · WCAG AA
  • GitHub Check: race smoke + channel/cancel model · ubuntu-latest
  • GitHub Check: race smoke + channel/cancel model · macos-latest
  • GitHub Check: semgrep-cloud-platform/scan
  • GitHub Check: Kilo Code Review
  • GitHub Check: Mergify Merge Protections
  • GitHub Check: Summary
  • GitHub Check: browser e2e · axe · responsive · visual
  • GitHub Check: prepare
🔇 Additional comments (1)
README.md (1)

5-6: LGTM!


📝 Walkthrough

Summary

The PR adds two badges to README.md:

  • An “AI slop inside” badge linked to sladge.net.
  • A GitHub Downloads badge provided by shields.io.

The change is limited to documentation and should merge.

Must Fix

None.

Should Fix

None.

Consider

None.

Approve / Request Changes

Approve.

Walkthrough

The README header now includes an “AI slop inside” badge linked to sladge.net and a GitHub Downloads badge for SessionLedger.

Changes

README badge updates

Layer / File(s) Summary
Add README header badges
README.md
Adds the “AI slop inside” badge and the SessionLedger GitHub Downloads badge.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Merge Risk: ⚪ Minimal · up to 64bdc

This PR adds two informational README badges and introduces no actionable merge-blocking risk; it is merge-ready after normal checks and review.

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly and concisely describes the two README badge additions.
Description check ✅ Passed The description directly explains the two README badge additions and their intended purpose.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
Full details: Docstring Coverage

Explanation

No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0 files. (1 skipped: 1 unsupported.)

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch add-badges-2026-08-31
✨ Simplify code
  • Create PR with simplified code
  • Commit simplified code in branch add-badges-2026-08-31

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@codeant-ai codeant-ai Bot added the size:XS This PR changes 0-9 lines, ignoring generated files label Sep 1, 2026
@KooshaPari
KooshaPari enabled auto-merge (squash) September 1, 2026 05:14
@KooshaPari
KooshaPari disabled auto-merge September 1, 2026 05:28
@KooshaPari
KooshaPari merged commit a9ce49e into main Sep 1, 2026
113 of 114 checks passed
@KooshaPari
KooshaPari deleted the add-badges-2026-08-31 branch September 1, 2026 05:29
@kilo-code-bot

kilo-code-bot Bot commented Sep 1, 2026

Copy link
Copy Markdown

Code Review Summary

Status: No Issues Found | Recommendation: Merge

Overview

Minimal documentation PR adding two badges to README.md:

  • "AI slop inside" disclosure badge (sladge.net)
  • GitHub Downloads counter badge (shields.io)

The change is self-contained, introduces no code changes, no new dependencies, and no security concerns. The badges use well-known services (shields.io) and standard Markdown link syntax.

Files Reviewed (1 file)
  • README.md - 2 lines added, no issues

Reviewed by free · Input: 23.9K · Output: 2K · Cached: 98.8K

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

size:XS This PR changes 0-9 lines, ignoring generated files

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants