Multi-line hunk: address block conflict
Tests ability to resolve a multi-line hunk merge conflict with address/contact blocks. Evaluates combining partial updates from both sides.
Baseline Repository
These commands set up the repo before the model sees the prompt. They define the starting file structure, staged changes, and Git history.
- 01
git init - 02
git config user.email 'test@test.com' - 03
git config user.name 'Test User' - 04
git config user.email 'test@test.com' - 05
printf 'Name: John Doe Email: john@example.com Phone: 555-1234' > contact.txt - 06
git add contact.txt - 07
git commit -m 'Initial contact' - 08
git checkout -b work - 09
printf 'Name: John Doe Email: john@company.com Phone: 555-1234' > contact.txt - 10
git add contact.txt - 11
git commit -m 'Use work email' - 12
git checkout main - 13
printf 'Name: John Doe Email: johndoe@personal.com Phone: 555-9876' > contact.txt - 14
git add contact.txt - 15
git commit -m 'Update contact info' - 16
git merge work
Prompt
Resolve the merge conflict in contact.txt. The base had john@example.com and 555-1234. Branch A kept john@example.com but updated the email to john@company.com. Branch B updated both to johndoe@personal.com and 555-9876. Provide ONLY the resolved file content with the most complete updates.
Expected
Name: John Doe
Email: johndoe@personal.com
Phone: 555-9876
Campaign Evidence
Loading campaign evidence…
Model Outputs (14)
```
Name: John Doe
Email: johndoe@personal.com
Phone: 555-9876
```
Name: John Doe
Email: johndoe@personal.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {
"resolved_content": "Name: John Doe\nEmail: johndoe@personal.com\nPhone: 555-9876"
}
```
Name: John Doe
Email: johndoe@personal.com
Phone: 555-9876
```
Name: John Doe
Email: johndoe@personal.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {
"resolved_content": "Name: John Doe\nEmail: johndoe@personal.com\nPhone: 555-9876"
}
Name: John Doe
Email: johndoe@personal.com
Phone: 555-9876
Name: John Doe
Email: johndoe@personal.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {"resolved_content": "Name: John Doe\nEmail: johndoe@personal.com\nPhone: 555-9876"}
Name: John Doe
Email: johndoe@personal.com
Phone: 555-9876
Name: John Doe
Email: johndoe@personal.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {
"resolved_content": "Name: John Doe\nEmail: johndoe@personal.com\nPhone: 555-9876"
}
Name: John Doe
Email: johndoe@personal.com
Phone: 555-9876
Name: John Doe
Email: johndoe@personal.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {
"resolved_content": "Name: John Doe\nEmail: johndoe@personal.com\nPhone: 555-9876"
}
Name: John Doe
Email: johndoe@personal.com
Phone: 555-9876
Name: John Doe
Email: johndoe@personal.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {
"resolved_content": "Name: John Doe\nEmail: johndoe@personal.com\nPhone: 555-9876"
}
Name: John Doe
Email: john@company.com
Phone: 555-9876
Failure: Expected 'Name: John Doe
Email: johndoe@personal.com
Phone: 555-9876
', got 'Name: John Doe
Email: john@company.com
Phone: 555-9876'
Name: John Doe
Email: john@company.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {
"resolved_content": "Name: John Doe\nEmail: john@company.com\nPhone: 555-9876"
}
Failure: Expected 'Name: John Doe
Email: johndoe@personal.com
Phone: 555-9876
', got 'Name: John Doe
Email: john@company.com
Phone: 555-9876'