Skip to content

chore(harness): correct PR title behavior #202

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
bougyman merged 2 commits into from
Sep 3, 2026
+5 −1
Merged

chore(harness): correct PR title behavior #202

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
c0fed0b
chore(harness): correct PR title behavior
ruby-automation Sep 3, 2026
130aa6a
Merge branch 'main' into guidance-for-pr-title
bougyman Sep 3, 2026
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: 5 additions & 1 deletion .ai/prompts/implement.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -23,6 +23,9 @@ Implement the solution, create a PR, and ensure it passes all quality checks.
Always sign git commits. If a gpg-agent is not available with a signing key,
stop and note that on the linear issue, do not create an unsigned commit.

Follow conventional commit message title rules for PR titles. This is
necessary for release-please to pick up our squash merge commits to main.

## First run

1. Read the investigation summary from the Linear comments.
Expand All @@ -38,8 +41,9 @@ stop and note that on the linear issue, do not create an unsigned commit.
7. Push the branch and create a PR:
```
git push -u origin HEAD
gh pr create --title "{{ issue.identifier }}: <concise title>" --body "<description>"
gh pr create --title "<type>(scope): <concise title>" --body "<description>"
```
We follow the same conventional commit message title for PR titles
8. Link the PR to the Linear issue.
9. Post a Linear comment with: what was done, what was tested, any known limitations.

Expand Down
Loading