Hotfix branch merged
Tests ability to identify a merged hotfix branch. Evaluates recognition of hotfix naming conventions in branch cleanup.
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.0' > version.txt - 05
git add version.txt - 06
git commit -m 'Release v1.0' - 07
git checkout -b hotfix-security - 08
echo 'v1.0.1-patched' > version.txt - 09
git add version.txt - 10
git commit -m 'Security patch' - 11
git checkout main - 12
git merge hotfix-security - 13
git checkout -b release-v2 - 14
echo 'v2.0-dev' > version.txt - 15
git add version.txt - 16
git commit -m 'Start v2.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
hotfix-security
Campaign Evidence
Loading campaign evidence…
Model Outputs (14)
hotfix-security
hotfix-security
hotfix-security
JSON Schema
Structured Output
(raw) {
"branches_to_delete": [
"hotfix-security"
]
}
hotfix-security
hotfix-security
JSON Schema
Structured Output
(raw) {"branches_to_delete": ["hotfix-security"]}
hotfix-security
hotfix-security
JSON Schema
Structured Output
(raw) {
"branches_to_delete": [
"hotfix-security"
]
}
hotfix-security
hotfix-security
JSON Schema
Structured Output
(raw) {
"branches_to_delete": [
"hotfix-security"
]
}
hotfix-security
hotfix-security
JSON Schema
Structured Output
(raw) {"branches_to_delete": ["hotfix-security"]}
hotfix-security
hotfix-security
JSON Schema
Structured Output
(raw) {"branches_to_delete": ["hotfix-security"]}
release-v2
JSON Schema
Structured Output
(raw) { "branches_to_delete": ["release-v2"] }
Failure: Missing: ['hotfix-security']
Extra: ['release-v2']