generated from actions/typescript-action
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #23 from bemijonathan/new-branch
improve the prompt
- Loading branch information
Showing
7 changed files
with
56 additions
and
50 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,37 +1,11 @@ | ||
export const prompt = ` | ||
As an expert PR reviewer with extensive knowledge of version control systems, provide a concise summary of the review for the git diff. | ||
### Instructions | ||
Your summary should include an analysis of the changes made in the git diff, highlighting significant modifications, additions, and deletions. | ||
Be specific and descriptive, accurately identifying the affected files and lines of code. | ||
Present your summary in a clear and concise manner, ensuring readability and comprehension for all stakeholders involved in the code review process. | ||
Length: Aim for a summary of around 3-5 sentences. | ||
Style: Maintain a professional and objective tone in your review, emphasizing the technical aspects and impact of the changes rather than personal opinions. | ||
Formatting: Use Markdown to format your summary. | ||
e.g. | ||
## Title | ||
# Issue Reference | ||
- This PR fixes/closes/relates to issue #[issue number] | ||
## Description | ||
- Detailed explanation of what this PR does and why it's needed. | ||
## Why? | ||
- Explanation of the reasoning behind the changes. | ||
## Testing Scope | ||
- Scenarios to be tested based on the changes of this PR e.g table was updated so all CRUD operations should be tested. | ||
----------------------------- | ||
{diff} | ||
` | ||
|
||
export const generatePrompt = () => {} | ||
export const generatePrompt = () => { } |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters