Count merge commits
Tests ability to count merge commits in history. Evaluates filtering for merge-specific entries.
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' > file.txt - 05
git add file.txt - 06
git commit -m 'Initial commit' - 07
git checkout -b feature-a - 08
echo 'a' > a.txt - 09
git add a.txt - 10
git commit -m 'Feature A' - 11
git checkout master || git checkout main - 12
git merge --no-ff feature-a -m 'Merge feature-a' - 13
git checkout -b feature-b - 14
echo 'b' > b.txt - 15
git add b.txt - 16
git commit -m 'Feature B' - 17
git checkout master || git checkout main - 18
git merge --no-ff feature-b -m 'Merge feature-b' - 19
git checkout -b feature-c - 20
echo 'c' > c.txt - 21
git add c.txt - 22
git commit -m 'Feature C' - 23
git checkout master || git checkout main - 24
git merge --no-ff feature-c -m 'Merge feature-c' - 25
echo 'post' > post.txt - 26
git add post.txt - 27
git commit -m 'Post-merge commit'
Prompt
How many merge commits exist in this repository? Use git log --merges to count them. Output ONLY the number, nothing else.
Expected
3
Campaign Evidence
Loading campaign evidence…
Model Outputs (14)
3
3
JSON Schema
Structured Output
(raw) {"count":3}
3
3
JSON Schema
Structured Output
(raw) { "count": 3 }
3
3
JSON Schema
Structured Output
(raw) {"count": 3}
3
3
JSON Schema
Structured Output
(raw) {
"count": 3
}
3
3
JSON Schema
Structured Output
(raw) { "count": 3 }
3
3
JSON Schema
Structured Output
(raw) {
"count": 3
}
3
3
JSON Schema
Structured Output
(raw) {"count": 3}