Skip to content

fix: preserve PR title across reviewer iterations #90

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
mdelapenya merged 1 commit into from
Mar 23, 2026
Merged

fix: preserve PR title across reviewer iterations #90

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 4 additions & 2 deletions prompts/reviewer-system.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -71,14 +71,16 @@ Before pushing, ensure the branch is clean:
- **Only if the push actually fails with a permission error should you handle workflow changes** (see "Handling Workflow File Push Failures" section below)
- If push succeeds, continue with PR creation below
- Generate a PR title using conventional commits format: `<type>: <description>`
- Infer the type from changes: `feat`, `fix`, `chore`, `refactor`, `docs`, `test`, `style`, `perf`, `build`, `ci`, `revert`
- **CRITICAL: The PR title must reflect the ENTIRE branch diff**, not just the latest iteration's work. Review ALL commits on the branch with `git log origin/__BASE_BRANCH__..HEAD --oneline` and `git diff origin/__BASE_BRANCH__..HEAD --stat` to understand the full scope of changes.
- If the branch already has a PR with a title (check `pr_number` in `.ralph/pr-info.txt` and read the existing title with `gh pr view <number> --repo <repo> --json title --jq '.title'`), **preserve the existing title unless the scope of changes has fundamentally changed** (e.g., a feat became a refactor). Minor follow-up work (style fixes, test additions, code review fixes) should NOT cause the title to change.
- Infer the type from the overall branch changes: `feat`, `fix`, `chore`, `refactor`, `docs`, `test`, `style`, `perf`, `build`, `ci`, `revert`
- Description must be lowercase and start with a verb
- Examples: `feat: add input validation to entrypoint`, `fix: resolve git safe directory error`
- Write the title to `.ralph/pr-title.txt`
- Build the PR body:
- "Closes #<issue_number>"
- Status and iteration count
- **Work summary:** Read `.ralph/work-summary.txt`. If empty or missing (e.g., retriggered action), generate a summary from git commit history using `git log origin/__BASE_BRANCH__..HEAD --oneline` and `git log origin/__BASE_BRANCH__..HEAD --format="%B"` to extract commit messages and understand what was done
- **Work summary:** Read `.ralph/work-summary.txt` AND review the full commit history with `git log origin/__BASE_BRANCH__..HEAD --oneline` and `git log origin/__BASE_BRANCH__..HEAD --format="%B"` to build a **comprehensive summary of ALL changes on the branch**, not just the latest iteration. If `.ralph/work-summary.txt` is empty or missing (e.g., retriggered action), generate the summary entirely from git commit history.
- Review feedback (if any)
- Footer: "_Generated by [Claude Ralph GitHub Action](https://github.com/mdelapenya/claude-ralph-github-action)_"
- If `pr_number` exists in pr-info.txt: Update it with `gh pr edit <number> --repo <repo> --title "<title>" --body "<body>"`
Expand Down
Loading