Feature: Exclude/Include users from report (#70)

* Feature: Exclude/Include users from report

* Fix: Correct unreviewed and unapproved calculations

Author: AlexSim93

README.md

@@ -97,7 +97,7 @@ Shows the total volume of code merged, reviews conducted, and comments in PRs. H
 | **dev3**  |        17        |        17        |         0          |       1        |        1         |      +1305/-310       |      14/1/1/0/1      |
 | **total** |        78        |        77        |         0          |       3        |        4         |      +8395/-3479      |     51/15/5/3/4      |
 
-### Discussion Intensity (Author’s Perspective)
+### 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.
 
@@ -118,7 +118,7 @@ title Discussions types total 12/2023
 "Formatting(9)":9
 ```
 
-### Discussion Intensity (Reviewer’s Perspective)
+### Discussion Intensity (Reviewer's Perspective)
 
 Measures how discussion-heavy PRs are from the reviewer's perspective, based on discussions, comments, and PR statuses. Helps understand reviewer engagement and decision-making. Use the `code-review-engagement` value in the `SHOW_STATS_TYPES` parameter and add thumbs up/down ( :+1: / :-1: ) reactions on opening comments.
 
@@ -333,6 +333,8 @@ Below is a table outlining the various configuration parameters available for **
 | `SHOW_USERS`                | Displays only specified users in reports, but includes all users in the background analytics. Use `total` to show total stats. Users should be separated by commas.                                                                                                                                                                                                                                   | -                                                                       |
 | `EXCLUDE_LABELS`            | PRs with mentioned labels will be excluded from the report . Values should be separated by commas. Example: `bugfix, enhancement`                                                                                                                                                                                                                                                                     | -                                                                       |
 | `INCLUDE_LABELS`            | Only PRs with mentioned labels will be included in the report. Values should be separated by commas. Example: `bugfix, enhancement`                                                                                                                                                                                                                                                                   | -                                                                       |
+| `INCLUDE_USERS`             | Only data for the specified users will be included in the report. Multiple values should be separated by commas. Example: `dev1, dev2`                                                                                                                                                                                                                                                            | -                                                                       |
+| `EXCLUDE_USERS`             | Data for the specified users will be excluded from the report. Multiple values should be separated by commas. Example: `dev1, dev2`                                                                                                                                                                                                                                                                 | -                                                                       |
 | `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

@@ -96,6 +96,12 @@ inputs:
   EXCLUDE_LABELS:
     description: "Excludes PRs with mentioned labels. Values should be separated by comma"
     required: false
+  INCLUDE_USERS:
+    description: "Only data for the specified users will be included in the report. Multiple values should be separated by commas"
+    required: false
+  EXCLUDE_USERS:
+    description: "Data for the specified users will be excluded from the report. Multiple values should be separated by commas"
+    required: false
   TIMEZONE:
     description: "Timezone to use in action"
     required: false