Feature: Configure discussion types

README.md

@@ -55,7 +55,7 @@ Shows the total volume of code merged, reviews conducted, and comments in PRs. H
 
 ### Discussion Intensity (Author's Perspective)
 
-Measures how discussion-heavy PRs are from the author's perspective, based on open discussions, review statuses, and the number of comments. Additionally, you can track discussion topics and user agreement by adding discussion topics in `[[]]` and using thumbs up/down ( :+1: / :-1: ) reactions on the opening comment. Use the `pr-quality` value in the `SHOW_STATS_TYPES` parameter.
+Measures how discussion-heavy PRs are from the author's perspective, based on open discussions, review statuses, and the number of comments. Additionally, you can analyze discussion-starting messages using the `DISCUSSION_TYPE_PATTERN` parameter and track user agreement using thumbs up/down ( :+1: / :-1: ) reactions on the opening comment. Use the `pr-quality` value in the `SHOW_STATS_TYPES` parameter.
 
 |   user    | Total merged PRs | Changes requested received | Agreed / Disagreed / Total discussions received | Comments received |
 | :-------: | :--------------: | :------------------------: | :---------------------------------------------: | :---------------: |
@@ -284,6 +284,7 @@ Below is a table outlining the various configuration parameters available for **
 | `EXCLUDE_USERS`             | Data for the specified users or teams will be excluded from the report. Multiple values should be separated by commas. Example: `dev1, dev2, team1`                                                                                                                                                                                                                                                   | -                                                                       |
 | `FILTER_HEAD_BRANCHES`      | Only PRs from head branches (source branches) matching the specified regular expression pattern will be included in the report. Example: `^feature`                                                                                                                                                                                                                                                   | -                                                                       |
 | `FILTER_BASE_BRANCHES`      | Only PRs to base branches (target branches) matching the specified regular expression pattern will be included in the report. Example: `^develop$`                                                                                                                                                                                                                                                    | -                                                                       |
+| `DISCUSSION_TYPE_PATTERN`   | Regex pattern to extract discussion types from review comments. If specified, matched values will be displayed in a separate table. The first capture group is used if present; otherwise, the full match is used. Example: `\\[\\[(.*?)\\]\\]`                                                                                                                                                       | -                                                                       |
 | `EXECUTION_OUTCOME`         | This parameter allows you to specify the format in which you wish to receive the report. Options include creating a new issue, updating an existing one, obtaining markdown, or JSON. Markdown and JSON will be available in outputs. Can take mulitple values separated by commas: `new-issue`, `markdown`, `collection`, `existing-issue`. This parameter is **required** Example: `existing-issue` | `new-issue`                                                             |
 | `ISSUE_NUMBER`              | Issue number to update. Add `existing-issue` to `EXECUTION_OUTCOME` for updating existing issue. The specified issue must already exist at the time the action is executed. This parameter is mandatory if the `EXECUTION_OUTCOME` input includes `existing-issue` value                                                                                                                              | -                                                                       |
 | `ALLOW_ANALYTICS`           | Allows sending non-sensitive inputs to mixpanel for better understanding user's needs. Set the value to `false` to disable sending action parameter data                                                                                                                                                                                                                                              | `true`                                                                  |

action.yml

@@ -138,6 +138,9 @@ inputs:
     description: "Shows activity time graphs"
     required: false
     default: false
+  DISCUSSION_TYPE_PATTERN:
+    description: "Regex pattern to extract discussion types from review comments"
+    required: false
 
 outputs:
   JSON_COLLECTION:

configs/yearReportWithoutDevelopers.yml

@@ -5,11 +5,11 @@ on:
       report_date_start:
         description: "Report date start(d/MM/yyyy)"
         required: false
-        default: "01/01/2024"
+        default: "01/01/2025"
       report_date_end:
         description: "Report date end(d/MM/yyyy)"
         required: false
-        default: "31/12/2024"
+        default: "31/12/2025"
       issue_title:
         description: "Issue title"
         required: false