Propagate dataset changes to dataset card

README.md

@@ -7,10 +7,10 @@ size_categories:
 - 10K<n<100K
 ---
 # Dataset Summary
-GitGoodBench Lite is a subset of 17492 samples for collecting trajectories of AI agents resolving git tasks (see Supported Scenarios) for model training purposes. 
+GitGoodBench Lite is a subset of 17469 samples for collecting trajectories of AI agents resolving git tasks (see Supported Scenarios) for model training purposes. 
 We support the programming languages Python, Java and Kotlin and the sample types merge conflict resolution and file-commit gram.
 
-All data in this dataset are collected from 829 unique, open-source GitHub repositories with permissive licenses 
+All data in this dataset are collected from 816 unique, open-source GitHub repositories with permissive licenses 
 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/)
 
 [For further details see our paper.]()
@@ -42,7 +42,7 @@ File-commit chain scenarios consist of two commits, the oldest and newest commit
 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 
 improve the local tree via rebasing. Thus samples of this `sample_type` cover two scenario types.
 
-File-commit chains are at least 3 commits long, all commits only contain files in the specified `programming_language` and no commit is a merge commit.
+File-commit chains are at least 3 commits long, the file the sample concerns itself with is guaranteed to be of `programming_language` (this is not the case for other potential files in the commits of the sample) and no commit is a merge commit.
 
 A `file_commit_chain` scenario looks as follows:
 ```