octokit retry plugin (#146)

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>

Author: harjotgill

action.yml

@@ -181,17 +181,14 @@ inputs:
       ```
 
       Format for changes and review comments (if any) -
-
-        ```new_hunk
-        <new code with line numbers for review>
+        ```new_hunk_for_review
+        <new code with line numbers>
         ```
-
-        ```old_hunk
-        <old code for context>
+        ```old_hunk_for_context
+        <old code>
         ```
-
-        ```comment_chain
-        <existing review comments for context>
+        ```comment_chains_for_context
+        <comment chains>
         ```
         ---
         ...
@@ -200,7 +197,6 @@ inputs:
       $patches
 
       Response format -
-
         <start_line_number>-<end_line_number>:
         <review>
         ```suggestion
@@ -217,32 +213,39 @@ inputs:
         ```
         ...
 
-      Example -
-
+      Example response -
         1-5:
         LGTM!
         ---
         6-6:
         ```suggestion
         print("Hello!")
         ```
+        ```go
+        log.Info().Msgf("Example")
+        ```
         ---
 
-      Your response must be in the above format. Each review section consists of a
-      line number range and a review comment applicable for that line 
-      number range. There is a separator between review sections. Any other text outside of this format will be 
-      ignored and will not be read by the parser. It's important that 
-      line number ranges for each review section must be within line 
-      number range of a specific new hunk. Don't echo back the code provided to you as the 
-      line number range is sufficient to map your review comment to the 
-      relevant code section in GitHub. Markdown format is preferred for 
-      text. Fenced code blocks must be used for new code and replacement 
-      code suggestions. Code replacement suggestions must be complete, 
-      correctly formatted and most importantly, map exactly to the line 
-      number ranges that need to be replaced inside the hunks. If there are no issues or 
-      suggestions and the hunk is acceptable as-is, your comment on the 
-      line ranges must include the word 'LGTM!'.
-
+      Instructions -
+      - Your response must be in the above format. Each review section 
+        consists of a line number range and a review comment applicable 
+        for that line number range. There is a separator between review 
+        sections. Any other text outside of this format will be 
+        ignored and will not be read by the parser. 
+      - It's important that line number ranges for each review section must 
+        be within the line number range of a specific new hunk, otherwise the 
+        comment can't be posted on GitHub. i.e. <start_line_number> should be
+        in the same hunk where <end_line_number> belongs to.
+      - Don't echo back the code provided to you as the line number range is 
+        sufficient to map your review comment to the relevant code section in 
+        GitHub. 
+      - Markdown format is preferred for text. 
+      - Fenced code blocks must be used for new code and replacement 
+        code suggestions. Code replacement suggestions must be complete, 
+        correctly formatted and most importantly, map exactly to the line 
+        number ranges that need to be replaced inside the hunks. 
+      - If there are no issues or suggestions and the hunk is acceptable as-is, 
+        your comment on the line ranges must include the word 'LGTM!'.
   comment:
     required: false
     description: 'Prompt for comment'
@@ -279,10 +282,10 @@ inputs:
       $diff
       ```
 
-      The format of the conversation chain is -
+      The format of a comment in the chain is -
       `user: comment`
 
-      Conversation chain (including the new comment) -
+      Comment chain (including the new comment) -
       ```
       $comment_chain
       ```