List commits in a date range
Tests ability to list commits in a date range. Evaluates time-based filtering with git log.
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_AUTHOR_DATE='2025-01-01T12:00:00' GIT_COMMITTER_DATE='2025-01-01T12:00:00' bash -c 'echo a > f.txt && git add f.txt && git commit -m "January commit"' - 05
GIT_AUTHOR_DATE='2025-02-01T12:00:00' GIT_COMMITTER_DATE='2025-02-01T12:00:00' bash -c 'echo b > f.txt && git add f.txt && git commit -m "February commit"' - 06
GIT_AUTHOR_DATE='2025-03-01T12:00:00' GIT_COMMITTER_DATE='2025-03-01T12:00:00' bash -c 'echo c > f.txt && git add f.txt && git commit -m "March commit"' - 07
GIT_AUTHOR_DATE='2025-04-01T12:00:00' GIT_COMMITTER_DATE='2025-04-01T12:00:00' bash -c 'echo d > f.txt && git add f.txt && git commit -m "April commit"'
Prompt
List all commits made between 2025-02-01 and 2025-03-31 (inclusive). Output ONLY the commit messages, one per line, nothing else.
Expected
February commit
March commit
Campaign Evidence
Loading campaign evidence…
Model Outputs (14)
February commit
March commit
February commit
March commit
JSON Schema
Structured Output
(raw) {"commit_message_list": ["February commit", "March commit"]}
February commit
March commit
February commit
March commit
JSON Schema
Structured Output
(raw) {
"commit_message_list": [
"February commit",
"March commit"
]
}
February commit
March commit
February commit
March commit
JSON Schema
Structured Output
(raw) {
"commit_message_list": [
"February commit",
"March commit"
]
}
February commit
March commit
March commit
February commit
Failure: Expected 'February commit
March commit', got 'March commit
February commit'
March commit
February commit
JSON Schema
Structured Output
(raw) {
"commit_message_list": [
"March commit",
"February commit"
]
}
Failure: Expected 'February commit
March commit', got 'March commit
February commit'
March commit
February commit
Failure: Expected 'February commit
March commit', got 'March commit
February commit'
March commit
February commit
JSON Schema
Structured Output
(raw) {"commit_message_list": ["March commit", "February commit"]}
Failure: Expected 'February commit
March commit', got 'March commit
February commit'
c3a6a944c845e3309cc8e6e76656cdb529de1ef9
eb3c63770b4ef621ccd003c101db519e1427225c
c5123c440bfbc522b085898f04b1f637264a5fb7
Failure: Expected 'February commit
March commit', got 'c3a6a944c845e3309cc8e6e76656cdb529de1ef9
eb3c63770b4ef621ccd003c101db519e1427225c
c5123c440bfbc522b085898f04b1f637264a5fb7'
Fourth commit
Third commit
Second commit
First commit
JSON Schema
Structured Output
(raw) {
"commit_message_list": [
"Fourth commit",
"Third commit",
"Second commit",
"First commit"
]
}
Failure: Expected 'February commit
March commit', got 'Fourth commit
Third commit
Second commit
First commit'
March commit
February commit
JSON Schema
Structured Output
(raw) {"commit_message_list": ["March commit", "February commit"]}
Failure: Expected 'February commit
March commit', got 'March commit
February commit'