Show merge commit and its parents
Tests ability to inspect a merge commit and identify its parents. Evaluates merge-commit structure comprehension.
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
echo 'base' > shared.txt - 05
git add shared.txt - 06
git commit -m 'Base commit' - 07
git checkout -b feature - 08
echo 'feature' > feature.txt - 09
git add feature.txt - 10
git commit -m 'Feature work' - 11
git checkout main - 12
echo 'main change' > shared.txt - 13
git add shared.txt - 14
git commit -m 'Main line work' - 15
git merge feature -m 'Merge feature branch'
Prompt
Using git show --merges -s --format=%P, how many parent commits does the merge commit have? Output ONLY the number, nothing else.
Expected
2
Campaign Evidence
Loading campaign evidence…
Model Outputs (14)
2
2
JSON Schema
Structured Output
(raw) {
"count": 2
}
2
2
JSON Schema
Structured Output
(raw) { "count": 2 }
2
2
JSON Schema
Structured Output
(raw) {"count": 2}
2
2
JSON Schema
Structured Output
(raw) {
"count": 2
}
2
2
JSON Schema
Structured Output
(raw) {
"count": 2
}
2
2
JSON Schema
Structured Output
(raw) {
"count": 2
}
2
2
JSON Schema
Structured Output
(raw) {"count": 2}