Skip to content

ci: daily stargazer export for the community star chart - #298

Merged
virtualsteve-exa merged 2 commits into
devfrom
ci/export-stargazers
Sep 30, 2026
Merged

virtualsteve-exa merged 2 commits into
devfrom
ci/export-stargazers

Conversation

@virtualsteve-exa

Copy link
Copy Markdown
Collaborator

Adds export-stargazers.yml, copied from Praxen's. It runs daily and publishes .github/stargazers.json to a force-pushed stargazer-export branch, since main only accepts PRs.

Why: the community stats site's star chart reads each repo's own export, because GitHub restricts the stargazers API to admins. Raffkin had no export, so the chart refresh has failed for all four projects since Raffkin was added. The "star-chart refresh failed — keeping prior SVG" warning is in the site's daily run.

It adds nothing to the plugin payload, so there's no version bump. It needs to be on main, because GitHub only runs scheduled workflows from the default branch.

🤖 Generated with Claude Code

https://claude.ai/code/session_016Q9UohWfy2scPhr4pavhqd

The community site's star chart reads each repo's own export, because GitHub restricts the
stargazers API to admins. Raffkin had no export, so the chart refresh failed for every project.
Same workflow as Praxen's: main is protected, so the export goes to a force-pushed
stargazer-export branch. It adds nothing to the plugin payload.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_016Q9UohWfy2scPhr4pavhqd
Signed-off-by: Steve Wilson <steve.wilson@exabeam.com>
@virtualsteve-exa
virtualsteve-exa merged commit 5477fb3 into dev Sep 30, 2026
5 checks passed
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