You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
"Prompt user to choose analysis mode for a pull request or issue."
209
212
;; DONE: add a choice: send out PR for current branch. The feature will ask user the target branch to merge. By default, it should be parent branch of current branch. AI should send out PR with description. The description should looks like it's written by the author, and it should be short.
213
+
;; DONE: for send out PR feature, it should ask user about the PR title. If user does not provide one, AI should generate a concise title based on the code change
210
214
(let* ((review-mode-alist '(("Review the PR". review-pr)
211
215
("Check unresolved feedback". check-feedback)
212
216
("Investigate issue". investigate-issue)
@@ -298,24 +302,32 @@ request or issue URL."
298
302
"Create the pull request using the backend's PR creation capability. "
299
303
"Do not treat this as a PR review flow before the PR exists."))))
"2. Generate a concise PR title based on the code change.\n"
315
+
(format"2. Use this PR title exactly: %s\n" pr-title))))
305
316
(format"Create a pull request from branch %s into %s.
306
317
307
318
%s
308
319
309
320
PR Creation Steps:
310
321
1. Inspect the current branch changes and open or send out a pull request into %s.
311
-
2. Write a concise PR description that sounds like it was written by the author, but do not make it too short.
312
-
3. Keep the description focused on the problem, the approach, and the most important verification, with enough detail for reviewers to understand the change quickly.
313
-
4. Aim for a compact but complete description, roughly a short summary plus 2 to 3 brief supporting paragraphs or bullet points.
314
-
5. Return the final PR URLand the exact description that was used."
322
+
%s3. Write a concise PR description that sounds like it was written by the author, but do not make it too short.
323
+
4. Keep the description focused on the problem, the approach, and the most important verification, with enough detail for reviewers to understand the change quickly.
324
+
5. Aim for a compact but complete description, roughly a short summary plus 2 to 3 brief supporting paragraphs or bullet points.
325
+
6. Return the final PR URL, the exact PR title, and the exact description that were used."
0 commit comments