Datasets:
Tasks:
Time Series Forecasting
Languages:
English
Size:
< 1K
Tags:
temporal-point-process
event-sequences
github
software-engineering
marked-temporal-point-process
License:
metadata
language:
- en
license: apache-2.0
task_categories:
- time-series-forecasting
tags:
- temporal-point-process
- event-sequences
- github
- software-engineering
- marked-temporal-point-process
size_categories:
- n<1K
GitHub Repository Event Streams
Curated event sequences from GitHub repositories, designed for temporal point process (TPP) and marked temporal point process (MTPP) modeling. Each sequence captures the development activity of a single repository over a one-week window.
Dataset Description
- Source: GH Archive raw JSON dumps
- Time window: June 1 - 7, 2024
- Grouping: Events grouped by repository
- Sequences: 373
- Sequence length: 60-80 events per sequence
- Time unit: hours
- Language: English only
Schema
Each record is a dictionary with 8 fields:
| Field | Type | Description |
|---|---|---|
seq_idx |
int | Sequence index |
seq_len |
int | Number of events in the sequence |
description |
str | Repository name, description, language, stars, and event window |
metadata |
str (JSON) | repo_name, stars, language, actors, time_unit |
time_since_start |
list[float] | Time since the first event (in time_unit, default hours) |
time_since_last_event |
list[float] | Time since the previous event (in time_unit, default hours) |
type_event |
list[str] | Event type labels (see below) |
type_text |
list[str] | Natural language description of each event |
Event Types (8 categories)
| Label | Description |
|---|---|
issue_opened |
New issue filed |
issue_closed |
Issue resolved/closed |
pr_opened |
Pull request opened |
pr_merged |
Pull request merged |
push |
Code pushed (with commit messages) |
release |
Release published |
pr_reviewed |
PR approved or changes requested |
comment |
Comment on issue, PR, or review |
Curation Filters
Sequences are selected to represent moderately active, well-maintained repositories with balanced development activity:
| Filter | Value | Description |
|---|---|---|
min-raw-events |
50 | Min kept-type events in archive (pre-classification) |
max-raw-events |
300 | Max kept-type events in archive (pre-classification) |
min-events |
60 | Min classified events per sequence |
max-events |
80 | Max classified events (skip, not truncate) |
max-bot-fraction |
0.2 | Skip repos where >20% events are from bots |
min-unique-types |
5 | At least 5 distinct event types |
min-avg-text-len |
150 | Min average text length per event |
max-type-fraction |
0.5 | No single event type >50% of events |
min-actors |
2 | At least 2 unique contributors |
max-actors |
5 | At most 5 unique contributors |
require-description |
true | Repo must have a description |
require-english |
true | All event texts must be in English (non-Latin script detection) |
Example
{
"seq_idx": 0,
"seq_len": 68,
"description": "GitHub repository example/repo: A web framework for building APIs (Python, 1,234 stars) Event window: June 01 - 07, 2024.",
"metadata": "{\"repo_name\": \"example/repo\", \"stars\": \"1234\", \"language\": \"Python\", \"actors\": [\"alice\", \"bob\", \"charlie\"], \"time_unit\": \"hours\"}",
"time_since_start": [0.0, 0.123, ...],
"time_since_last_event": [0.0, 0.123, ...],
"type_event": ["pr_opened", "comment", "pr_reviewed", ...],
"type_text": ["Pull request opened by alice: Add new RPC endpoint...", ...]
}
Intended Use
- Training and evaluating temporal point process models
- Studying software development workflow patterns
- Benchmarking next-event prediction and event forecasting
- Modeling marked temporal point processes with rich text marks
Citation
If you use this dataset, please cite:
@dataset{github_repo_events_2024,
title={GitHub Repository Event Streams},
author={XiaoBB},
year={2024},
url={https://huggingface.co/datasets/XiaoBB/github_repo_events},
note={Curated from GH Archive, June 2024}
}