Datasets:

helloadhavan
/

github_issues

@@ -65,49 +65,55 @@ size_categories:
 - 10K<n<100K
 ---
-# GitHub Issues + Fixes Dataset
-A **curated, high-signal dataset** of GitHub issues collected from **25 popular open-source repositories**.
-Each example pairs a real GitHub issue with the **exact code changes (diffs)** that resolved it.
-The dataset is designed for:
-- **Automated bug fixing**
-- **LLM-based code agents**
-- **Issue → patch generation**
-- **Program repair research**
 ---
-## How the data was extracted
-The data was collected using the **GitHub REST API** and processed into a structured format.
 To maintain quality and usefulness:
-- Only **closed issues** were considered
-- Each issue must have a **clearly associated fix**
-- Fixes are stored as **unified diffs** extracted from the resolving commit
-- Low-signal issues (questions, duplicates, discussions) were filtered out
-- Issues without meaningful code changes were excluded
-Each row represents **one issue–fix pair**.
 ---
-## Dataset structure
-Each dataset entry has the following schema:
 ```json
 {
   "repo": "owner/repository",
-  "issue_number": 12345,
-  "issue_title": "Short description of the problem",
-  "issue_body": "Full issue discussion and problem description",
-  "commit_sha": "abcdef123456...",
   "files": [
     {
       "filename": "path/to/file.ext",
-      "patch": "unified diff showing the fix",
       "additions": 10,
       "deletions": 2
     }
@@ -115,19 +121,21 @@ Each dataset entry has the following schema:
 }
 ```
-| Field               | Description                                  |
-| ------------------- | -------------------------------------------- |
-| `repo`              | GitHub repository where the issue originated |
-| `issue_number`      | Original GitHub issue number                 |
-| `issue_title`       | Title of the issue                           |
-| `issue_body`        | Full issue description and context           |
-| `commit_sha`        | Commit that fixed the issue                  |
-| `files`             | List of modified files                       |
-| `files[].filename`  | Path of the modified file                    |
-| `files[].patch`     | Unified diff representing the fix            |
-| `files[].additions` | Number of added lines                        |
-| `files[].deletions` | Number of removed lines                      |
 ## Supported languages
@@ -147,22 +155,23 @@ Language distribution varies by repository.
 This dataset is well-suited for:
-* Training models to generate code patches from issue descriptions
-* Evaluating LLM reasoning over real-world bug reports
-* Building autonomous debugging or refactoring agents
-* Research on program repair, code synthesis, and software maintenance
-It is **not** intended for:
-* Issue classification
-* sentiment analysis
-* Chatbot fine-tuning without code generation
 ## Limitations
-* The dataset reflects real-world noise from GitHub issues
-* Issue descriptions vary widely in clarity and detail
-* Some fixes involve refactoring or design changes rather than minimal patches
-* No guarantee that all fixes are optimal or best practice
-> **<span style="color:red;font-size:1.25rem">Warning</span>**: This dataset currently has the issues of 10/25 repos and 14k rows but is expected to have 50k rows and 2 GB in size

 - 10K<n<100K
 ---
+# GitHub Pull Request Bug–Fix Dataset
+A **curated, high-signal dataset of real-world software bugs and fixes** collected from **25 popular open-source GitHub repositories**.
+Each entry corresponds to a **single pull request (PR)** and pairs contextual metadata with the **exact code changes (unified diffs)** that fixed the bug.
+This dataset is designed for:
+- **Automated program repair**
+- **Bug-fix patch generation**
+- **LLM-based code and debugging agents**
+- **Empirical software engineering research**
 ---
+## Data collection methodology
+Data was collected using the **GitHub REST API** and post-processed into a structured format.
 To maintain quality and usefulness:
+- Only **merged pull requests** were included
+- Each PR must represent a **bug fix or correctness change**
+- Fixes are linked to both the **buggy commit** and the **fix commit**
+- Code changes are stored as **unified diffs** at the file level
+- Low-signal PRs (refactors, formatting-only changes, discussions) were filtered out
+- PRs without meaningful code changes were excluded
+Each dataset row represents **one bug–fix PR**.
 ---
+## Dataset schema
+Each entry follows the schema below:
 ```json
 {
   "repo": "owner/repository",
+  "pr_number": 12345,
+  "title": "Short description of the fix",
+  "body": "Pull request description and context",
+  "buggy_commit": "abcdef123456...",
+  "fix_commit": "fedcba654321...",
+  "buggy_distance": 12,
+  "confidence": "medium",
   "files": [
     {
       "filename": "path/to/file.ext",
+      "patch": "unified diff representing the fix",
       "additions": 10,
       "deletions": 2
     }
 }
 ```
+| Field               | Description                                       |
+| ------------------- | ------------------------------------------------- |
+| `repo`              | GitHub repository containing the pull request     |
+| `pr_number`         | Pull request number                               |
+| `title`             | Pull request title                                |
+| `body`              | Pull request description and discussion context   |
+| `buggy_commit`      | Commit introducing or containing the bug          |
+| `fix_commit`        | Commit that fixes the bug                         |
+| `buggy_distance`    | Number of commits between buggy and fix commits   |
+| `confidence`        | Heuristic confidence level of bug–fix correctness |
+| `files`             | List of files modified by the fix                 |
+| `files[].filename`  | Path to the modified file                         |
+| `files[].patch`     | Unified diff containing the code changes          |
+| `files[].additions` | Number of lines added                             |
+| `files[].deletions` | Number of lines removed                           |
 ## Supported languages
 This dataset is well-suited for:
+* Training models to generate patches from real pull request context
+* Studying bug-fix patterns across large codebases
+* Building autonomous debugging or repair agents
+* Research in program repair, code synthesis, and software maintenance
+It is not intended for:
+* Pull request classification or triage
+* Sentiment analysis
+* General-purpose chatbot fine-tuning without code generation objectives
 ## Limitations
+The dataset reflects real-world noise from GitHub pull requests
+Buggy commit identification is heuristic and may be imperfect
+Some fixes involve refactoring or design changes rather than minimal patches
+No guarantee that fixes represent optimal or best-practice solutions
+> ⚠️ Warning
+This dataset currently includes pull requests from 10 of the planned 25 repositories, totaling approximately 24,000 entries.
+The final release is expected to contain ~50,000 entries and occupy ~2 GB of storage.