Release v1.12.5

Report Presentation and Documentation Enhancements

• Enhanced Report Text and Column Descriptions: Updated the text in reports for better clarity and understanding. Added detailed descriptions for each column, providing a clearer understanding of the data presented.

• Improved Report Configuration Format: Refined the configuration formation within reports for enhanced readability and comprehension. This update makes it easier for users to understand the specific settings used for each report.

• Streamlined Comment Reports: Removed the display of configuration settings in report comments to avoid redundancy. This change declutters the report presentation, focusing solely on the analytics.

• Updated Documentation and Examples: Thoroughly revised the documentation and updated examples to reflect the latest changes and functionalities. This ensures users have access to the most current information and guidance on using pull-request-analytics-action.

Release v1.12.4

Improved GitHub Organization Support

• Enhanced Handling of Large Organizations: Significantly improved the functionality of pull-request-analytics-action with larger GitHub organizations. The action now supports requesting data from more than 100 repositories within a single organization. This upgrade caters to the needs of larger teams and organizations, ensuring comprehensive analytics coverage regardless of the size of the organization.

Release v1.12.3

Feature Enhancement

• Gantt Chart Value Formatting: Enhanced the Gantt chart in the pull-request-analytics-action by introducing improved formatting for the values displayed. This update ensures that the data on the Gantt chart is presented more clearly and effectively, aiding in the easy interpretation and analysis of project timelines and durations.

Release v1.12.2

Improvements and Fixes

• Optional GITHUB_REPO_FOR_ISSUE and GITHUB_OWNER_FOR_ISSUE Inputs: Updated the action to make GITHUB_REPO_FOR_ISSUE and GITHUB_OWNER_FOR_ISSUE inputs optional. This change applies when creating or updating an issue for the report is not required, streamlining the configuration process for reports that don't involve issue manipulation.

• Enhanced Validation Warnings: Improved the validation process to provide more accurate and helpful warnings. This ensures users are better informed about any potential configuration issues before execution.

• Time to Approval and Review Calculation Update: Fixed the calculation of time to approval and time to review. If a review or approval does not occur, the time is now considered equivalent to the merge time. This adjustment provides a more realistic representation of timelines in scenarios where reviews or approvals are pending at the time of merging.

Release v1.12.1

Enhancement

• Incorporated PERIOD_SPLIT_UNIT in Report Parameters: Added the PERIOD_SPLIT_UNIT to the list of applied parameters in reports. This update ensures that users have clear visibility of how reports are segmented based on the specified period unit, whether it's years, quarters, or months. This enhancement enhances transparency and aids in understanding the structure and basis of the analytics presented.

Release v1.12.0

Feature Update and Bug Fix

• New PERIOD_SPLIT_UNIT Parameter: Enhanced the report customization by introducing the PERIOD_SPLIT_UNIT parameter. This addition allows for dividing the report into different periods such as years, quarters, or months. Users can also select 'none' to avoid period segmentation altogether. This feature offers greater flexibility in tailoring the report structure to specific analytical needs.

• Resolved Report Period Behavior: Fixed an issue where setting both REPORT_PERIOD and REPORT_DATE_END would lead to inconsistent behavior. This correction ensures more accurate report generation when specific date ranges are defined, enhancing the reliability of the analytics.

Release v1.11.0

Feature Enhancement

• Updated Issue Reporting with ISSUE_NUMBER Input: Implemented a new feature that allows for updating an existing issue instead of creating a new one for each report. This is achieved by adding the ISSUE_NUMBER input, which works in conjunction with the existing-issue value in EXECUTION_OUTCOME. This update provides a more streamlined and organized approach to report generation, reducing clutter and enhancing continuity in issue tracking.

Release v1.10.0

New Input Feature

• Introduced REPORT_PERIOD Variable: Added the REPORT_PERIOD variable to facilitate the creation of reports for the most recent time periods. This variable accepts units such as years, months, weeks, days, hours, minutes, and seconds. This enhancement simplifies the action setup and enables the automated generation of reports at regular intervals, making it more flexible and user-friendly for continuous analytics.

Release v1.9.0

Documentation Update and New Features

• Updated Documentation and Simplified Example Configuration: Revised the documentation to reflect the latest functionalities and improvements. Additionally, the configuration example has been simplified for easier understanding and implementation.

• New ORGANIZATIONS Input Added: Introduced the ORGANIZATIONS input option. This allows users to gather data for all repositories within a specified organization, eliminating the need for manually listing individual owners and repositories. This enhancement streamlines the data collection process for organizational analytics.

• Weekend Time Calculation Fix and Graph Visibility Adjustment: Corrected the time calculation to account for actions taken during weekends. Also implemented a feature that hides graphs if all users lack sufficient data for accurate representation. This ensures clarity and relevance in the displayed analytics.

Release v1.8.4

New Feature Added

• Enhanced Analysis of Discussion Reactions: Implemented a new functionality in pull-request-analytics-action to track and display 👍 and 👎 reactions on the initial messages of discussions. These reactions are now shown in the "discussions received" and "discussions conducted" columns of the report. This enhancement allows for a more nuanced understanding of the community's response to each discussion topic. By analyzing these reactions, users can assess the effectiveness and reception of their discussions, gaining valuable insights into the most engaging and useful topics.