PR Title Check / check-title (pull_request) Successful in 8s
Test Python Package / unit-tests (pull_request) Successful in 13s
Code Quality Pipeline / code-quality (pull_request) Successful in 23s
Test Python Package / integration-tests (pull_request) Successful in 1m14s
Test Python Package / coverage-report (pull_request) Successful in 12s
Record the one-to-one unit test file convention in README and add rules for test placement and copy-ready PR text after first push. Co-authored-by: Cursor <[email protected]>
59 lines
1.6 KiB
Plaintext
59 lines
1.6 KiB
Plaintext
---
|
|
description: After first branch push, provide copy-ready PR title and body
|
|
alwaysApply: true
|
|
---
|
|
|
|
# PR Title and Comment After First Push
|
|
|
|
The user creates pull requests manually. After the **first push** of a feature branch to remote in a session, always end your response with a copy-ready PR title and PR comment.
|
|
|
|
## When to provide it
|
|
|
|
- After the first successful `git push` (or `git push -u origin <branch>`) for a branch in the current task
|
|
- Do **not** create the PR with `gh pr create` unless explicitly asked
|
|
- On later pushes to the same branch, only repeat if the user asks or the change set meaningfully updates what the PR should say
|
|
|
|
## PR title
|
|
|
|
- Use a fitting version-bump prefix when changes touch `python_repositories/`:
|
|
- `[patch]` or `[fix]` — bug fix
|
|
- `[minor]` or `[feat]` — new feature
|
|
- `[major]` or `[breaking]` — breaking change
|
|
- Docs-, CI-, or test-only changes: no prefix required
|
|
- Keep the title concise and descriptive
|
|
|
|
## PR comment format
|
|
|
|
Provide two separate fenced code blocks the user can copy directly:
|
|
|
|
1. **PR title** — single line in a code block
|
|
2. **PR comment** — body with `## Summary` and `## Test plan` sections, checklist items reflecting what was actually run
|
|
|
|
Example structure:
|
|
|
|
````
|
|
PR title:
|
|
|
|
```
|
|
[minor] Short description of the change
|
|
```
|
|
|
|
PR comment:
|
|
|
|
```
|
|
## Summary
|
|
|
|
- Bullet points of what changed and why
|
|
|
|
## Test plan
|
|
|
|
- [x] Commands or checks that were run
|
|
```
|
|
````
|
|
|
|
## Notes
|
|
|
|
- Match the repo PR template ([`.gitea/PULL_REQUEST_TEMPLATE.md`](.gitea/PULL_REQUEST_TEMPLATE.md))
|
|
- Be accurate: only mark test-plan items done if they were run
|
|
- Keep prose clear; the user copies this verbatim into Gitea
|