newsletter-cache-refresh

Automating GitHub repository activity data collection involves running a Python script to fetch commits, PRs, issues, and releases, storing them as JSON files under a dated cache directory like .cache/YYYY-MM. This automatically generates a summary.json and per-repo data files to support consistent downstream reporting.

The SCRC activity data cache includes a summary.json file and individual per-repo JSON files containing commits, PRs, issues, and releases data. These files are organized under a .cache/YYYY-MM/ directory structure to support analytics and reconciliation across three specific repositories.

Yes, you can generate cache data for a custom date range by passing optional start and end dates to the fetch activity script. You can also configure a custom output directory to fit your specific workflow and reporting needs.

Yes, the uv runtime is required to execute the fetch_activity script. You run the cache refresh tool using the command format uv run python tools/newsletter/fetch_activity.py --month YYYY-MM to populate the necessary cache directories.

Refreshing the activity data cache automatically ensures consistent analytics and reporting across multiple repositories. It fetches the latest commits, PRs, issues, and releases, storing them in structured JSON files to prevent data misalignment in downstream newsletter generation.