fix(tool): chart only this repo — the workflow token can't read siblings

[abdulsaheel]

User description

Follow-up to #155. I test-ran the new workflow after merging and it failed on its first live run — and the fail-closed behaviour CodeRabbit asked for in #155 is precisely why we found out cleanly instead of silently shipping a worse chart.

What happened

A workflow's built-in GITHUB_TOKEN is scoped to its own repository. Reading OpenStrap/protocol from a job running in OpenStrap/edge returns 403:

OpenStrap/edge: 334 stars
error: gh api repos/OpenStrap/protocol/stargazers?per_page=100&page=1 failed:
  gh: Resource not accessible by integration (HTTP 403)
  — aborting rather than publishing a partial chart

Which is exactly the right outcome. Under the original warn-and-continue version, this would have quietly generated an edge-only chart, committed it over the good three-series one, and logged nothing that looked like a problem. CodeRabbit's finding earned its keep within the hour.

Fix

Default to charting this repo alone, which works with the built-in token. The repo list now comes from STAR_HISTORY_REPOS, so siblings can be added later by supplying a PAT with read access — opt-in, rather than a default that 403s:

STAR_HISTORY_REPOS="OpenStrap/edge,OpenStrap/protocol" python3 tool/gen_star_history.py

Verified both paths: default → edge · 334; override → edge · 334 + protocol · 11.

Why the committed SVG changed too

It has to. If local output and CI output disagree on the repo set, the SVG flip-flops between one and three series and the workflow commits a revision every week — the exact churn the no-change guard exists to stop. Regenerated so the two are byte-identical. Re-confirmed determinism across consecutive runs.

Honestly the single-series chart also reads better: protocol (11) and analytics (5) were near-flat lines against edge's 334, so they added noise more than information.

Captions in the README and on the landing page updated to say what the chart covers and how to widen it.

Docs + one script. No Dart touched.

---

PR Type

Bug fix

---

Description

• Fix CI failure: default to charting only OpenStrap/edge (built-in token scope)

• Make repo list configurable via STAR_HISTORY_REPOS env var for opt-in PAT use

• Update README and landing page captions to reflect single-repo chart

• Regenerate committed SVG so local and CI output are byte-identical

---

Diagram Walkthrough

flowchart LR
  A["STAR_HISTORY_REPOS env var\n(optional, PAT required)"]
  B["gen_star_history.py\ndefault: OpenStrap/edge only"]
  C["docs/star-history.svg\n(single-series chart)"]
  D["CI workflow\n(built-in GITHUB_TOKEN)"]
  A -- "override with PAT" --> B
  D -- "runs with default" --> B
  B -- "generates" --> C

Loading

File Walkthrough

	Relevant files
Bug fix	gen_star_history.py Make repo list env-configurable, default to edge only        tool/gen_star_history.py Replaced hardcoded three-repo list with a single default (OpenStrap/edge) Made repo list configurable via STAR_HISTORY_REPOS environment variable Added detailed comment explaining why the default is load-bearing (token scope, flip-flop risk) +15/-1
Documentation	README.md Update README captions for single-repo star chart                README.md Updated alt text on star-history image to reflect single-repo chart Added explanation that built-in token can't read sibling repos Documented STAR_HISTORY_REPOS opt-in for cross-repo PAT usage +4/-2      index.html Update landing page image alt text for single-repo chart  docs/index.html Updated alt attribute on star-history image to say OpenStrap/edge only +1/-1

---

[coderabbitai]

Warning

Review limit reached

@abdulsaheel, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 25 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 089abe12-7129-4080-93eb-6eb431d17dd8

📥 Commits

Reviewing files that changed from the base of the PR and between 4d8899f and 56b6653.

⛔ Files ignored due to path filters (1)

• docs/star-history.svg is excluded by !**/*.svg

📒 Files selected for processing (3)

• README.md
• docs/index.html
• tool/gen_star_history.py

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix/star-history-token

---

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

[github-actions]

PR Reviewer Guide 🔍

Here are some key observations to aid the review process:

⏱️ Estimated effort to review: 1 🔵⚪⚪⚪⚪

🧪 No relevant tests

🔒 No security concerns identified

⚡ No major issues detected

[github-actions]

PR Code Suggestions ✨

No code suggestions found for the PR.