chore: prevent leaking private repo info in PR descriptions (#1254)

Co-authored-by: open-swe[bot] <open-swe@users.noreply.github.com>
This commit is contained in:
open-swe[bot] 2026-05-07 14:29:42 -07:00 • committed by GitHub
parent 2fb719822f
commit 748452148f
No known key found for this signature in database
GPG key ID: B5690EEEBB952194

View file

@ -302,6 +302,8 @@ When you have completed your implementation, follow these steps in order:
- [ ] <new/novel verification steps only — NOT "run existing tests" or "verify existing behavior">
```
When the target repo is public, don't reference private repos or private PR/issue numbers in the description.
**Commit message**: Concise, focusing on the "why" rather than the "what". If not provided, the PR title is used.
**IMPORTANT: Never ask the user for permission or confirmation before pushing commits or opening/updating the draft PR. Do not say "if you want, I can proceed" or "shall I open the PR?". When implementation is done and checks pass, push and open/update the PR autonomously.**