Hugging Face's logo

Datasets:
JetBrains
/
git_good_bench-lite

Modalities:
Tabular
Text
Formats:
csv
Size:
< 1K
Tags:
git
code
Libraries:
Datasets
pandas
License:
Dataset card Data Studio Files
xet
Community
1
Liqs commited on
Commit
8bdc90b
·
verified ·
1 Parent(s): 69f75b9

Create dataset fact sheet

Browse files
Files changed (1) hide show
  1. README.md +108 -3
README.md CHANGED
@@ -1,3 +1,108 @@
1
- ---
2
- license: apache-2.0
3
- ---
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ ---
2
+ license: apache-2.0
3
+ tags:
4
+ - git
5
+ - software-engineering
6
+ size_categories:
7
+ - n<1K
8
+ ---
9
+ # Dataset Summary
10
+ GitGoodBench Lite is a subset of 120 samples for evaluating the performance of AI agents in resolving git tasks (see Supported Scenarios).
11
+ The samples in the dataset are evenly split across the programming languages Python, Java and Kotlin and the sample types merge conflict resolution and file-commit gram.
12
+ This dataset thus contains 20 samples per sample type and programming language.
13
+
14
+ All data in this dataset are collected from open-source repositories on GitHub with permissive licenses
15
+ that have >= 1000 stars, >= 5 branches, >= 10 contributors and are not a fork or archived. We collected the initial list of repositories using [SEART.](https://seart-ghs.si.usi.ch/)
16
+
17
+ Evaluation is to be performed by exact-match (EM) of diffs for the merge conflict setting and by LLM-as-a-Judge for the file-commit gram setting. [For further details see our paper.]()
18
+
19
+ # Supported Tasks
20
+ GitGoodBench Lite contains two types of samples: 'merge' and 'file_commit_chain'. All data required to setup the preconditions for a scenario are located in the `scenario` field.
21
+ It is important to note that the sample type 'file_commit_chain' can be used for two scenario types: Performing an interactive rebase to clean up the local tree or iteratively
22
+ generating commits based on the staged, uncommitted changes.
23
+
24
+ ## Merge
25
+ Merge scenarios are contain one or more merge conflicts that occurred during a merge. All merge conflicts are guaranteed to be in a Python, Java or Kotlin file. There are only
26
+ merges with exactly two parents in our dataset (no octopus merges).
27
+
28
+ A merge scenario looks as follows:
29
+ ```
30
+ {
31
+ 'merge_commit_hash': 'baa37f65fdff5b780a50d5b5c6bf8bc3ade43815',
32
+ 'parents': ['d758810c59a9134f437d60f73a82036749688ccb', '5dcd493c67ff863c69c1214f0892a80e4951087e'],
33
+ 'number_of_files_with_merge_conflict': 2,
34
+ 'total_number_of_merge_conflicts': 2,
35
+ 'files_in_merge_conflict': ['cogs/gpt_3_commands_and_converser.py', 'models/openai_model.py']
36
+ }
37
+ ```
38
+
39
+ Where `merge_commit_hash` contains the ground truth merge commit and the `parents` are the commits during the merge of which the conflict(s) in `files_in_merge_conflict` occurred.
40
+
41
+ ## File-Commit Chain
42
+ File-commit chain scenarios consist of two commits, the oldest and newest commit. In all commits between the `oldest_commit` and `newest_commit` (inclusive) `file` was modified.
43
+ In total the chain consists of `times_seen_consecutively` commits. The intended use-cases of these scenarios are to evaluate the agent's capacity to create meaningful, cohesive commits or
44
+ improve the local tree via rebasing. Thus samples of this `sample_type` cover two scenario types.
45
+
46
+ A `file_commit_chain` scenario looks as follows:
47
+ ```
48
+ {
49
+ 'file': 'composer/models/huggingface.py',
50
+ 'branch': 'origin/vincent-mlflow-logger-verbose',
51
+ 'times_seen_consecutively': 3,
52
+ 'purity': 0.68,
53
+ 'newest_commit': 'c24b29f19c4c131a3ea7098dd8b8a5edde344819',
54
+ 'oldest_commit': 'c1ff80900f46d4e36feb4b326689fe14fc41cbc6'
55
+ }
56
+ ```
57
+
58
+ `purity` indicates the relative amount of changes in the chain that occurred solely in `file` and is a heuristic for the difficulty of the scenario. We expect noisier scenarios to be more difficult.
59
+
60
+ # Dataset Structure
61
+ The following table provides per-field details. Columns marked “Yes” under **Is Metadata?** are those that provide contextual or descriptive information but are not essential to the primary scenario logic.
62
+
63
+ | **Field** | **Type** | **Description** | **Is Metadata?** |
64
+ |--------------------------|------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------|
65
+ | **id** | string | A unique identifier for the dataset entry: <name>-<sample_type>-<running_index> | No |
66
+ | **name** | string | The repository name, in “owner/repository” format. | No |
67
+ | **default_branch** | string | The primary or default branch for the repository. | No |
68
+ | **license** | string | Repository license. | Yes |
69
+ | **stargazers** | integer | The number of stars on GitHub. | Yes |
70
+ | **created_at** | string | The repository creation date. | Yes |
71
+ | **topics** | string | A semicolon-delimited list of topics or tags associated with the repository. | Yes |
72
+ | **programming_language** | string | The programming language of the sample. Possible values: "java," "python," or "kotlin." | No |
73
+ | **scenario** | string | A JSON string describing specific scenario data (e.g., merge-conflict details, parent commits). | No |
74
+ | **sample_type** | string | The type of sample. Possible values: "merge" or "file_commit_chain." | No |
75
+ | **project_size** | string | Estimated size based on lines of code. Possible values: "tiny," "small," "medium," "large," or "huge." | Yes |
76
+ | **project_activity** | string | How recently the project was active. Possible values: "day," "week," or "month." | Yes |
77
+ | **difficulty** | string | The complexity level of the scenario. Possible values: "easy," "medium," or "hard." | Yes |
78
+
79
+ **Note**:
80
+ - Fields marked as **Is Metadata? = Yes** provide contextual information (e.g., project stats, licensing) rather than forming the core logic of a scenario.
81
+ - Fields marked **No** represent the primary data for the scenario. Use them to inform or categorize the scenario type and project details.
82
+
83
+ # Dataset statistics
84
+ We provide some statistics on the distribution of “difficulty” within the overall dataset and across different scenario types.
85
+
86
+ ## Overall Difficulty Distribution
87
+ | Difficulty | Fraction |
88
+ |------------|----------|
89
+ | easy | 0.375000 |
90
+ | medium | 0.333333 |
91
+ | hard | 0.291667 |
92
+
93
+ ## Difficulty Distribution for "merge" Scenarios
94
+ | Difficulty | Fraction |
95
+ |------------|----------|
96
+ | easy | 0.516667 |
97
+ | hard | 0.266667 |
98
+ | medium | 0.216667 |
99
+
100
+ ## Difficulty Distribution for "file_commit_chain" Scenarios
101
+ | Difficulty | Fraction |
102
+ |------------|----------|
103
+ | medium | 0.450000 |
104
+ | hard | 0.316667 |
105
+ | easy | 0.233333 |
106
+
107
+
108
+ **Languages** We note that the text data in this dataset consists mostly of: commit messages, comments and is primarily in English. We do however not filter for any human languages explcitly.