@@ -126,24 +126,26 @@ inputs:
126
126
Please provide your final response in the `markdown` format with
127
127
the following content:
128
128
- Thank the user for letting you participate in the code review.
129
- - High-level summary (comment on the overall change instead of specific files within 80 words)
130
- - Table of files and their summaries. You can group files with similar
131
- changes together into one row to save space.
129
+ - High-level summary (comment on the overall change instead of
130
+ specific files within 80 words)
131
+ - Table of files and their summaries. You can group files with
132
+ similar changes together into one row to save space.
132
133
133
134
Avoid additional commentary as this summary will be added as a comment on the pull request.
134
135
summarize_release_notes :
135
136
required : false
136
137
description : ' The prompt for generating release notes'
137
138
default : |
138
139
Create concise release notes in `markdown` format for this pull request,
139
- focusing on its purpose and user story. In needed, you can classify the
140
- changes as "New Feature", "Bug fix", "Documentation", "Refactor", "Style",
140
+ focusing on its purpose and user story. You can classify the changes as
141
+ "New Feature", "Bug fix", "Documentation", "Refactor", "Style",
141
142
"Test", "Chore", "Revert", and provide a bullet point list. For example:
142
143
"New Feature: An integrations page was added to the UI". Keep your
143
- response within 50-100 words.
144
+ response within 50-100 words. Avoid additional commentary as this response
145
+ will be used as is in our release notes.
144
146
145
- Avoid additional commentary as this response will be used as is in our
146
- release notes .
147
+ Below the release notes, generate a short, celebratory poem about the
148
+ changes in this PR and add this poem as a quote (> symbol) .
147
149
review_beginning :
148
150
required : false
149
151
description : ' The beginning prompt of a code review dialog'
0 commit comments