gitwal
GitHub event archive
The purpose of gitwal is to make it easy to answer questions that would otherwise take thousands of GitHub API requests. Questions like:
- Who starred a repo, and when?Everyone who starred
reactin January 2016. - Is a dependency dying?80% of last year's merges came from one person.
- What is breaking out right now?Repos accelerating against every peer.
- Which companies build in this ecosystem?Every org with
kubernetespull requests.
Each event carries type event_id ts actor_id actor_login repo_id repo_name org_id org_login schema, plus the fields below.
| Event type | Events | Additional fields |
|---|---|---|
WatchEventStar | 548,704,884 | None |
ForkEventFork | 175,632,040 | forkee_idforkee_name |
CreateEventRepository created | 412,705,890 | ref_type |
PublicEventRepository made public | 28,192,628 | None |
ReleaseEventRelease published | 53,454,344 | actiontag_nameprerelease |
MemberEventCollaborator added or removed | 36,748,340 | actionmember_idmember_login |
PullRequestEventPull request opened, closed or merged | 822,004,754 | actionnumberpr_idmergedmerged_atadditionsdeletionschanged_files |
IssuesEventIssue opened or closed | 285,297,320 | actionnumberissue_id |
IssueCommentEventComment on an issue or pull request | 559,249,241 | actionnumberissue_idcomment_idon_pull_request |
PullRequestReviewEventPull request review | 171,888,001 | actionnumberreview_idreview_state |
Refreshed: 2026-09-18T22:24:10.829Z