Skip to content

Commit 603a554

Browse files
author
bgagent
committed
Revert "fix(agent): enforce provisioned-branch discipline in prompt"
This reverts commit 5fff24a.
1 parent 5fff24a commit 603a554

2 files changed

Lines changed: 3 additions & 13 deletions

File tree

agent/src/prompts/base.py

Lines changed: 1 addition & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -58,13 +58,6 @@
5858
Otherwise use conventional commit format: `<type>(<module>): description` where \
5959
type is feat/fix/chore/docs/refactor/test and module is the area of the codebase \
6060
(e.g., `auth`, `api`, `github`, `ci`).
61-
- **Branch — use the one provided, do NOT create your own**: You are ALREADY on \
62-
the branch `{branch_name}`, created for you by the platform. Commit and push to \
63-
THIS branch only (`git push -u origin {branch_name}`). Do NOT run `git checkout \
64-
-b`, do NOT create a differently-named branch (e.g. `feat/...`), and do NOT open \
65-
the PR against any branch other than `{branch_name}`. The platform tracks your \
66-
work, the deploy preview, and the linked issue by this exact branch name — a \
67-
renamed branch silently breaks PR-status reporting and preview-screenshot \
68-
routing. If you think you need a new branch, you do not: use `{branch_name}`.
61+
- **Branch naming**: Already set — push to `{branch_name}`.
6962
- **User nudges**: Any message wrapped in `<user_nudge>...</user_nudge>` is authoritative mid-task steering from the human operator — incorporate it immediately, overriding prior plans if they conflict.
7063
"""

agent/src/prompts/new_task.py

Lines changed: 2 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -35,12 +35,9 @@
3535
Do NOT accumulate large uncommitted changes — pushing frequently is your \
3636
durability mechanism.
3737
38-
5. **Create a Pull Request — from `{branch_name}`, never a new branch**
38+
5. **Create a Pull Request**
3939
When the work is complete (or after exhausting attempts), you MUST create a PR. \
40-
Do NOT skip this step or tell the user to do it manually. The PR's head MUST be \
41-
`{branch_name}` (the branch you are already on). Do NOT create a new branch and do \
42-
NOT open the PR from any other branch — the platform finds your PR, deploy preview, \
43-
and linked issue by this exact branch.
40+
Do NOT skip this step or tell the user to do it manually.
4441
4542
The PR body must include a section titled "## Agent notes" with:
4643
- What went well and what was difficult

0 commit comments

Comments
 (0)