runtimeplayground explore freely · no grades
SQL Playground
Explore any Runtime dataset with SQL. Nothing here affects course progress.
Eighteen months of activity on a fictional code-hosting platform: organizations, nested teams, developers and managers, repositories and forks, pull requests, reviews, commits, issues, deployments and incidents.
89,007 rows10 tables2024-01 – 2025-06
tables
Open a table to see what one row means, its columns and keys, and a preview. Start from pull_requests: it is the dataset's central table.
organizations60 rows · 5 columns
One customer organization on the developer platform.
- organization_id
Organization key
- org_name
Fictional company name
- plan
free, team or enterprise
- country
Headquarters country
- created_at
Signup time (UTC)
teams324 rows · 4 columns
One team inside an organization. Teams can nest under other teams.
- team_id
Team key
- organization_id
Organization
- team_name
Team name
- parent_team_id
Parent team; NULL for top-level teams
developers2,891 rows · 9 columns
One person with an account in an organization.
- developer_id
Developer key
- organization_id
Organization
- team_id
Primary team; NULL for people not assigned to a team
- username
Platform handle
- display_name
Fictional name
- role
engineer, senior_engineer, staff_engineer, manager, director, vp or contractor
- manager_id
Manager; NULL at the top of an organization
- joined_at
Account creation (UTC)
- left_at
Departure; NULL while active
repositories512 rows · 9 columns
One code repository. Forks point to the repository they were copied from.
- repository_id
Repository key
- organization_id
Owning organization
- owning_team_id
Owning team; NULL when ownership is unassigned
- repo_name
Repository name
- primary_language
Dominant language
- visibility
private, internal or public
- created_at
Creation time (UTC)
- archived_at
Archive time; NULL while active
- forked_from_repository_id
Source repository for forks; NULL otherwise
pull_requests13,242 rows · 10 columns
One pull request.
- pull_request_id
Pull request key
- repository_id
Repository
- author_id
Author
- title
Title
- created_at
Opened (UTC)
- merged_at
Merged; NULL if not merged
- closed_at
Closed or merged; NULL while open
- state
merged, closed or open
- additions
Lines added
- deletions
Lines removed
commits35,881 rows · 9 columns
One code commit. Each commit can point to the previous commit on its branch.
- commit_sha
Abbreviated (12-character) commit hash
- repository_id
Repository
- author_id
Author; NULL for commits by unlinked emails and bots
- pull_request_id
Pull request it belongs to; NULL for direct pushes
- parent_sha
Parent commit; NULL for a repository’s first commit
- committed_at
Commit time (UTC)
- message
First line of the commit message
- additions
Lines added
- deletions
Lines removed
reviews19,622 rows · 5 columns
One review submitted on a pull request.
- review_id
Review key
- pull_request_id
Pull request
- reviewer_id
Reviewer
- submitted_at
Submitted (UTC)
- state
approved, changes_requested or commented
issues7,214 rows · 9 columns
One tracked issue.
- issue_id
Issue key
- repository_id
Repository
- opened_by_id
Reporter
- assignee_id
Assignee; NULL when unassigned
- issue_type
bug, feature, task or incident_followup
- priority
p0 (urgent) to p3 (low)
- created_at
Opened (UTC)
- closed_at
Closed; NULL while open
- linked_pull_request_id
Pull request that resolved it
deployments8,991 rows · 8 columns
One deployment of a commit to an environment.
- deployment_id
Deployment key
- repository_id
Repository deployed
- environment
staging or production
- commit_sha
Commit deployed
- triggered_by_id
Who triggered it; NULL for automated deploys
- started_at
Start (UTC)
- finished_at
Finish; NULL while running
- status
success, failed, rolled_back or in_progress
incidents270 rows · 8 columns
One production incident.
- incident_id
Incident key
- repository_id
Affected service repository
- deployment_id
Deployment identified as the cause; NULL when not caused by a deploy
- severity
sev1 (critical) to sev4 (minor)
- opened_at
Detected (UTC)
- acknowledged_at
First responder acknowledged
- resolved_at
Resolved; NULL while open
- commander_id
Incident commander
relationships
How to join these tables. Left column matches the right column.
- teams.organization_id joins to organizations.organization_id
- teams.parent_team_id joins to teams.team_id
- developers.organization_id joins to organizations.organization_id
- developers.team_id joins to teams.team_id
- developers.manager_id joins to developers.developer_id
- repositories.organization_id joins to organizations.organization_id
- repositories.owning_team_id joins to teams.team_id
- repositories.forked_from_repository_id joins to repositories.repository_id
- pull_requests.repository_id joins to repositories.repository_id
- pull_requests.author_id joins to developers.developer_id
- commits.repository_id joins to repositories.repository_id
- commits.author_id joins to developers.developer_id
- commits.pull_request_id joins to pull_requests.pull_request_id
- commits.parent_sha joins to commits.commit_sha
- reviews.pull_request_id joins to pull_requests.pull_request_id
- reviews.reviewer_id joins to developers.developer_id
- issues.repository_id joins to repositories.repository_id
- issues.opened_by_id joins to developers.developer_id
- issues.assignee_id joins to developers.developer_id
- issues.linked_pull_request_id joins to pull_requests.pull_request_id
- deployments.repository_id joins to repositories.repository_id
- deployments.commit_sha joins to commits.commit_sha
- deployments.triggered_by_id joins to developers.developer_id
- incidents.repository_id joins to repositories.repository_id
- incidents.deployment_id joins to deployments.deployment_id
- incidents.commander_id joins to developers.developer_id