Skip to content

cli.md

Latest commit

 

History

History
71 lines (55 loc) · 1.82 KB

cli.md

File metadata and controls

71 lines (55 loc) · 1.82 KB
Raw

GitHub Activity Stream — Apify CLI examples

Call the hosted GitHub Activity Stream from your terminal with the Apify CLI. These commands run the Actor on Apify — nothing scrapes locally.

Install & log in

npm install -g apify-cli
apify login   # paste your Apify API token (apify.com → Settings → Integrations)

Run with default input (popular default repo)

apify call logiover/github-activity-stream

Single repo — one week of all activity

apify call logiover/github-activity-stream \
  --input='{
    "mode": "repo",
    "repos": ["microsoft/vscode"],
    "eventTypes": ["commits", "pulls", "issues", "releases"],
    "since": "2026-06-29",
    "maxPerType": 200
  }'

Org-wide scan — only PRs and releases

apify call logiover/github-activity-stream \
  --input='{
    "mode": "org",
    "org": "kubernetes",
    "maxOrgRepos": 15,
    "eventTypes": ["pulls", "releases"],
    "since": "2026-06-01"
  }'

User public activity

apify call logiover/github-activity-stream \
  --input='{ "mode": "user", "user": "torvalds", "maxPerType": 100 }'

Bulk multi-repo release watch

apify call logiover/github-activity-stream \
  --input='{
    "mode": "bulk",
    "repos": ["facebook/react", "vercel/next.js", "microsoft/typescript"],
    "eventTypes": ["releases"],
    "since": "2026-06-01"
  }'

Download the dataset after a run

apify runs ls
apify datasets get-items <DATASET_ID> --format=csv > activity.csv
apify datasets get-items <DATASET_ID> --format=json > activity.json

Tip: set since to your last run time on every scheduled run so each pull is a clean delta. Trim eventTypes to ["releases"] when you only track versions — commits are the slowest, highest-volume type.