Skip to content

xtask: add generated badge endpoints#605

Merged
EffortlessSteven merged 3 commits into
mainfrom
docs/generated-badge-endpoints
May 13, 2026
Merged

xtask: add generated badge endpoints#605
EffortlessSteven merged 3 commits into
mainfrom
docs/generated-badge-endpoints

Conversation

@EffortlessSteven

Copy link
Copy Markdown
Member

Summary

  • add generated Shields endpoint JSON for ripr+ and scanner-safe fixture status
  • add cargo xtask badges / --check to refresh or verify committed badge endpoints
  • update the README badge cluster to use downloads, ripr+, and scanner-safe endpoints

Validation

  • cargo xtask badges
  • cargo xtask badges --check
  • cargo test -p xtask badge
  • cargo xtask docs-sync --check

Notes

  • The ripr+ endpoint is repo-scoped and generated via ripr check --root . --format repo-badge-plus-shields.
  • The scanner-safe endpoint is generated from the no-blob fixture scan; failure writes the red debug endpoint only under target/xtask/badges and fails before updating committed badge JSON.

@gemini-code-assist

Copy link
Copy Markdown

Warning

You have reached your daily quota limit. Please wait up to 24 hours and I will start processing your requests again!

@coderabbitai

coderabbitai Bot commented May 12, 2026

Copy link
Copy Markdown

Warning

Rate limit exceeded

@EffortlessSteven has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 51 minutes and 27 seconds before requesting another review.

You’ve run out of usage credits. Purchase more in the billing tab.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: 56e1c11a-7e6c-49ee-8f06-e5b235cf60c9

📥 Commits

Reviewing files that changed from the base of the PR and between a8a32b9 and 815b715.

📒 Files selected for processing (4)
  • README.md
  • badges/ripr-plus.json
  • badges/scanner-safe.json
  • xtask/src/main.rs
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch docs/generated-badge-endpoints

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 and usage tips.

@chatgpt-codex-connector chatgpt-codex-connector Bot 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.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: d9db1e0be0

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread xtask/src/main.rs Outdated
fn ripr_plus_badge() -> Result<ShieldsEndpointBadge> {
let ripr_bin = env::var("RIPR_BIN").unwrap_or_else(|_| "ripr".to_string());
let output = Command::new(&ripr_bin)
.args(["check", "--root", ".", "--format", "repo-badge-plus-shields"])

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P2 Badge Resolve badge generation from the workspace root

When cargo xtask badges is invoked from a workspace subdirectory such as xtask/, this --root . points ripr at only that subdirectory, and the surrounding badge reads/writes also use subdirectory-relative badges/ and target/xtask/badges. In that context the command can report success while creating xtask/badges/* and leaving the public repo-root /badges endpoints stale; root the command and badge paths via workspace_root_path() instead.

Useful? React with 👍 / 👎.

@EffortlessSteven EffortlessSteven merged commit 5bd50dd into main May 13, 2026
6 checks passed
@EffortlessSteven EffortlessSteven deleted the docs/generated-badge-endpoints branch May 13, 2026 00:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant