Skip to content

AiratTop/github-repo-stats

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

8 Commits
 
 
 
 
 
 

Repository files navigation

GitHub Repo Stats

github-repo-stats

This repository collects and stores long-term GitHub repository analytics for the public repositories of AiratTop using the github-repo-stats GitHub Action.

Features

  • Long-term history: Stores repository traffic snapshots over time, beyond GitHub’s default short retention window.
  • Multi-repository tracking: Collects analytics for multiple public repositories from a single workflow.
  • Automatic updates: Runs daily on a scheduled GitHub Actions workflow.
  • Manual runs: Supports manual workflow execution with workflow_dispatch.
  • Centralized storage: Stores generated data and reports in a dedicated branch of this repository.
  • Simple setup: Works with a single GitHub token stored in repository secrets.
  • Public and free-friendly: Well suited for tracking public repositories with GitHub-hosted runners.

Tracked Repository Groups

Profile

Self-hosted

API

Tools / Web Apps / Services

Utility / Misc

Workflow

This repository uses a GitHub Actions workflow located at:

.github/workflows/repo-stats.yml

The workflow:

  1. Runs daily on schedule.
  2. Can be started manually from the GitHub Actions tab.
  3. Iterates through the configured list of repositories.
  4. Collects repository traffic and related analytics.
  5. Stores the generated data in a dedicated branch.

Data Storage

Generated analytics data is stored in a separate branch:

github-repo-stats

This keeps the main branch clean while allowing the action to continuously append and update analytics artifacts over time.

Requirements

  • A public GitHub repository for storing workflow configuration and generated analytics.
  • A GitHub personal access token stored in repository secrets.
  • Repository secret name:
GHRS_GITHUB_API_TOKEN

Usage

Run manually

  1. Open the Actions tab in this repository.
  2. Select the repo-stats workflow.
  3. Click Run workflow.

Wait for scheduled collection

The workflow also runs automatically every day based on the configured cron schedule.

Notes

  • The first useful analytics history appears only after multiple workflow runs.
  • The repository accumulates snapshots over time, so the value grows gradually.
  • This setup is intended for public repositories and a simple, low-maintenance analytics workflow.

License

This project is licensed under the MIT License - see the LICENSE file for details.


Author

AiratTop

Sponsor this project

Contributors