blob: 4c13c0ded42ed76e1d49e5e8d7145a3e5efb413f (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
|
prompt: >
Write a clear, informative pull request message in markdown:
* Start with a summary
* Remember to mention the files that were changed, and what was changed
* Explain the 'why' behind changes
* Include a bulleted list to outline all of the changes
* If there are no changes, or the input is blank - then return a blank string
Think carefully before you write your pull request body.
What you write will be passed to create a github pull request
Text to use for the pull request message: $input
|
