Update paper link, task categories and add sample usage

#1
by nielsr HF Staff - opened
Files changed (1) hide show
  1. README.md +32 -14
README.md CHANGED
@@ -1,20 +1,23 @@
1
  ---
2
- pretty_name: SWE-CI
3
- license: apache-2.0
4
- version: 1.0.0
5
  language:
6
  - en
 
 
 
 
 
 
 
7
  tags:
8
  - code
9
  - agent
10
- size_categories:
11
- - n<1K
12
  ---
 
13
  # SWE-CI: Evaluating Agent Capabilities in Maintaining Codebases via Continuous Integration
14
 
15
  🔗 Github Link: [https://github.com/SKYLENAGE-AI/SWE-CI](https://github.com/SKYLENAGE-AI/SWE-CI)
16
 
17
- 🔗 Paper Link: Coming soon ...
18
 
19
  *🏆 What is SWE-CI? A Coding benchmark for continuous integration*
20
 
@@ -31,9 +34,30 @@ SWE-CI introduces four key shifts:
31
  * **From Snapshots to Evolution**: Instead of fixing a single bug, SWE-CI focuses on the trajectory between two commits (from ‘current’ commit to ‘target’ commits). It models how codebases actually grow, refactor, and evolve over time.
32
  * **From Static Descriptions to CI-Driven Requirements**: Instead of relying on human-written issue descriptions, SWE-CI uses the "Test Gap" as the primary driver. By running the Target Tests on the Current Source, we generate raw CI failure reports. In the SWE-CI framework, an Architect Agent then translates these technical logs into natural language requirements, which a Programmer Agent uses to implement the changes.
33
  * **Iterative Refinement (The CI Loop)**: SWE-CI is built for a closed-loop evaluation. The model doesn't just "guess" the fix; it must interact with the environment, analyze test failures, and refine the code iteratively—exactly like a developer working against a CI pipeline.
34
-
35
  * **From One-off Fixes to Sustainable Maintenance**: SWE-CI emphasizes the long-term maintainability of the software. It evaluates whether agents can accurately comprehend complex systems and propose the most essential requirements. It challenges agents to write readable and extensible code that facilitates future evolution cycles, rather than just "hacking" a solution that passes the current tests but hinders future growth.
36
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
37
 
38
  ## Dataset description
39
 
@@ -55,9 +79,6 @@ SWE-CI-full contains a total of 137 tasks. Each task consists of three parts: me
55
 
56
  For more detailed information: including the data collection, cleaning, and filtering processes, the construction of environment images, and further explanations of the metadata, please refer to our paper.
57
 
58
-
59
-
60
-
61
  ## Licensing
62
 
63
  This dataset is released under a multi-licensing model to account for the different sources and types of content:
@@ -71,12 +92,9 @@ The source code contained in `code.zip` consists of sampled files from various o
71
  * **Ownership:** These files remain the property of their original authors.
72
  * **License:** They are governed by the **original open-source licenses** (e.g., MIT, Apache 2.0, BSD) of the respective upstream projects.
73
  * **Disclaimer:** We redistribute these code snippets for research and benchmarking purposes under the redistribution permissions granted by their original licenses.
74
- Content Removal
75
  * **Content Removal:** We respect open-source intellectual property. If you are a copyright holder and wish to have your repository removed from this dataset, please open an Issue in the "Community" tab of this Hugging Face repository. We will process valid requests promptly.
76
 
77
-
78
-
79
  ### 3. Environment Images (`/data/**/image.tar.gz` files)
80
  The pre-built Docker images are provided as **Aggregate Works** for reproducibility.
81
  * **Curation Work:** The logic, environment configurations (e.g., specific library versions, dependency resolution), and setup scripts integrated within these images are licensed under the **Apache License 2.0**.
82
- * **Third-Party Components:** The underlying Operating System (e.g., Debian/Ubuntu), system libraries, and pre-installed packages within the images are subject to their own respective upstream licenses.
 
1
  ---
 
 
 
2
  language:
3
  - en
4
+ license: apache-2.0
5
+ size_categories:
6
+ - n<1K
7
+ task_categories:
8
+ - text-generation
9
+ pretty_name: SWE-CI
10
+ version: 1.0.0
11
  tags:
12
  - code
13
  - agent
 
 
14
  ---
15
+
16
  # SWE-CI: Evaluating Agent Capabilities in Maintaining Codebases via Continuous Integration
17
 
18
  🔗 Github Link: [https://github.com/SKYLENAGE-AI/SWE-CI](https://github.com/SKYLENAGE-AI/SWE-CI)
19
 
20
+ 🔗 Paper Link: [https://huggingface.co/papers/2603.03823](https://huggingface.co/papers/2603.03823)
21
 
22
  *🏆 What is SWE-CI? A Coding benchmark for continuous integration*
23
 
 
34
  * **From Snapshots to Evolution**: Instead of fixing a single bug, SWE-CI focuses on the trajectory between two commits (from ‘current’ commit to ‘target’ commits). It models how codebases actually grow, refactor, and evolve over time.
35
  * **From Static Descriptions to CI-Driven Requirements**: Instead of relying on human-written issue descriptions, SWE-CI uses the "Test Gap" as the primary driver. By running the Target Tests on the Current Source, we generate raw CI failure reports. In the SWE-CI framework, an Architect Agent then translates these technical logs into natural language requirements, which a Programmer Agent uses to implement the changes.
36
  * **Iterative Refinement (The CI Loop)**: SWE-CI is built for a closed-loop evaluation. The model doesn't just "guess" the fix; it must interact with the environment, analyze test failures, and refine the code iteratively—exactly like a developer working against a CI pipeline.
 
37
  * **From One-off Fixes to Sustainable Maintenance**: SWE-CI emphasizes the long-term maintainability of the software. It evaluates whether agents can accurately comprehend complex systems and propose the most essential requirements. It challenges agents to write readable and extensible code that facilitates future evolution cycles, rather than just "hacking" a solution that passes the current tests but hinders future growth.
38
 
39
+ ## Sample Usage
40
+
41
+ ### Installation
42
+ ```bash
43
+ git clone https://github.com/SKYLENAGE-AI/SWE-CI.git
44
+ cd SWE-CI
45
+
46
+ conda create --name sweci python=3.11 -y
47
+ conda activate sweci
48
+ pip install -r requirements.txt
49
+ ```
50
+
51
+ ### Download the Dataset
52
+ ```bash
53
+ # Using default parameters
54
+ PYTHONPATH=src python -m swe_ci.download
55
+
56
+ # Using custom parameters
57
+ PYTHONPATH=src python -m swe_ci.download \
58
+ --splitting full \
59
+ --hf_token <HF_TOKEN>
60
+ ```
61
 
62
  ## Dataset description
63
 
 
79
 
80
  For more detailed information: including the data collection, cleaning, and filtering processes, the construction of environment images, and further explanations of the metadata, please refer to our paper.
81
 
 
 
 
82
  ## Licensing
83
 
84
  This dataset is released under a multi-licensing model to account for the different sources and types of content:
 
92
  * **Ownership:** These files remain the property of their original authors.
93
  * **License:** They are governed by the **original open-source licenses** (e.g., MIT, Apache 2.0, BSD) of the respective upstream projects.
94
  * **Disclaimer:** We redistribute these code snippets for research and benchmarking purposes under the redistribution permissions granted by their original licenses.
 
95
  * **Content Removal:** We respect open-source intellectual property. If you are a copyright holder and wish to have your repository removed from this dataset, please open an Issue in the "Community" tab of this Hugging Face repository. We will process valid requests promptly.
96
 
 
 
97
  ### 3. Environment Images (`/data/**/image.tar.gz` files)
98
  The pre-built Docker images are provided as **Aggregate Works** for reproducibility.
99
  * **Curation Work:** The logic, environment configurations (e.g., specific library versions, dependency resolution), and setup scripts integrated within these images are licensed under the **Apache License 2.0**.
100
+ * **Third-Party Components:** The underlying Operating System (e.g., Debian/Ubuntu), system libraries, and pre-installed packages within the images are subject to their own respective upstream licenses.