Release branches
Tests ability to identify merged release branches for cleanup. Evaluates release-branch lifecycle management.
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 'v1' > version.txt - 05
git add version.txt - 06
git commit -m 'v1.0' - 07
git checkout -b release-1.0 - 08
echo 'v1.0' > release.txt - 09
git add release.txt - 10
git commit -m 'Release 1.0' - 11
git checkout main - 12
git merge release-1.0 - 13
git checkout -b release-2.0 - 14
echo 'v2.0' > release.txt - 15
git add release.txt - 16
git commit -m 'Release 2.0' - 17
git checkout main
Prompt
Look at the branches in this repository. Which branches should be deleted because they are fully merged into main? List ONLY the branch names to delete, one per line. If none, respond with 'none'.
Expected
release-1.0
Campaign Evidence
Loading campaign evidence…
Model Outputs (14)
release-1.0
release-1.0
release-1.0
JSON Schema
Structured Output
(raw) { "branches_to_delete": ["release-1.0"] }
release-1.0
release-1.0
JSON Schema
Structured Output
(raw) {"branches_to_delete": ["release-1.0"]}
release-1.0
release-1.0
JSON Schema
Structured Output
(raw) {
"branches_to_delete": [
"release-1.0"
]
}
release-1.0
JSON Schema
Structured Output
(raw) {
"branches_to_delete": [
"release-1.0"
]
}
release-1.0
release-1.0
JSON Schema
Structured Output
(raw) {"branches_to_delete": ["release-1.0"]}
release-1.0
release-1.0
release-2.0
JSON Schema
Structured Output
(raw) {"branches_to_delete": ["release-1.0", "release-2.0"]}
Failure: Extra: ['release-2.0']
Invalid JSON. Output:
JSON Schema
Structured Output
Structured Output Error
Failed to parse structured JSON response: Expecting value: line 1 column 1 (char 0)
Failure: Failed to parse structured JSON response: Expecting value: line 1 column 1 (char 0)
none
Failure: Missing: ['release-1.0']
Extra: ['none']