From 96707b588e4d7bc2669ad7b77119988ccf8374b8 Mon Sep 17 00:00:00 2001 From: Srinath Padmanabhan <17151014+srithreepo@users.noreply.github.com> Date: Sat, 30 Aug 2025 08:43:54 -0700 Subject: [PATCH] Update Issue Triage (#7469) --- .../gemini-automated-issue-triage.yml | 15 +++++++++++---- .../gemini-scheduled-issue-triage.yml | 18 ++++++++++++------ 2 files changed, 23 insertions(+), 10 deletions(-) diff --git a/.github/workflows/gemini-automated-issue-triage.yml b/.github/workflows/gemini-automated-issue-triage.yml index 3823fbb543..7e40675318 100644 --- a/.github/workflows/gemini-automated-issue-triage.yml +++ b/.github/workflows/gemini-automated-issue-triage.yml @@ -159,7 +159,8 @@ jobs: {"labels_to_set": [], "explanation": "Unable to classify this issue with available labels"} ``` 9. Use Area definitions mentioned below to help you narrow down issues. - 10. If you are uncertain and have not been able to apply one each of kind/, area/ and priority/ , apply the status/manual-triage label. + 10. If you think an issue might be a Priority/P0 do not apply the priority/p0 label. Instead apply a status/manual-triage label and include a note in your explanation. + 11. If you are uncertain and have not been able to apply one each of kind/, area/ and priority/ , apply the status/manual-triage label. ## Guidelines @@ -176,7 +177,10 @@ jobs: Categorization Guidelines: P0: Critical / Blocker - - A P0 bug is a catastrophic failure that demands immediate attention. It represents a complete showstopper for a significant portion of users or for the development process itself. + - A P0 bug is a catastrophic failure that demands immediate attention. + - To be a P0 it means almost all users are running into this issue and it is blocking users from being able to use the product. + - You would see this in the form of many comments from different developers on the bug. + - It represents a complete showstopper for a significant portion of users or for the development process itself. Impact: - Blocks development or testing for the entire team. - Major security vulnerability that could compromise user data or system integrity. @@ -185,14 +189,17 @@ jobs: Qualifier: Is the main function of the software broken? Example: The gemini auth login command fails with an unrecoverable error, preventing any user from authenticating and using the rest of the CLI. P1: High - - A P1 bug is a serious issue that significantly degrades the user experience or impacts a core feature. While not a complete blocker, it's a major problem that needs a fast resolution. Feature requests are almost never P1. + - A P1 bug is a serious issue that significantly degrades the user experience or impacts a core feature. + - While not a complete blocker, it's a major problem that needs a fast resolution. Feature requests are almost never P1. + - Once again this would be affecting many users. + - You would see this in the form of comments from different developers on the bug. Impact: - A core feature is broken or behaving incorrectly for a large number of users or large number of use cases. - Review the bug details and comments to try figure out if this issue affects a large set of use cases or if it's a narrow set of use cases. - Severe performance degradation making the application frustratingly slow. - No straightforward workaround exists, or the workaround is difficult and non-obvious. Qualifier: Is a key feature unusable or giving very wrong results? - Example: The gemini -p "..." command consistently returns a malformed JSON response or an empty result, making the CLI's primary generation feature unreliable. + Example: Gemini CLI enters a loop when making read-many-files tool call. I am unable to break out of the loop and gemini doesn't follow instructions subsequently. P2: Medium - A P2 bug is a moderately impactful issue. It's a noticeable problem but doesn't prevent the use of the software's main functionality. Impact: diff --git a/.github/workflows/gemini-scheduled-issue-triage.yml b/.github/workflows/gemini-scheduled-issue-triage.yml index 3ff2ab6abc..a716b83f10 100644 --- a/.github/workflows/gemini-scheduled-issue-triage.yml +++ b/.github/workflows/gemini-scheduled-issue-triage.yml @@ -146,7 +146,8 @@ jobs: - Anything more than 6 versions older than the most recent should add the status/need-retesting label 11. If you see that the issue doesn't look like it has sufficient information recommend the status/need-information label and leave a comment politely requesting the relevant information, eg.. if repro steps are missing request for repro steps. if version information is missing request for version information into the explanation section below. - After identifying appropriate labels to an issue, add "status/need-triage" label to labels_to_remove in the output. - 12. If you are uncertain and have not been able to apply one each of kind/, area/ and priority/ , apply the status/manual-triage label. + 12. If you think an issue might be a Priority/P0 do not apply the priority/p0 label. Instead apply a status/manual-triage label and include a note in your explanation. + 13. If you are uncertain and have not been able to apply one each of kind/, area/ and priority/ , apply the status/manual-triage label. ## Guidelines @@ -162,8 +163,11 @@ jobs: - Once you categorize the issue if it needs information bump down the priority by 1 eg.. a p0 would become a p1 a p1 would become a p2. P2 and P3 can stay as is in this scenario. Categorization Guidelines: P0: Critical / Blocker - - A P0 bug is a catastrophic failure that demands immediate attention. It represents a complete showstopper for a significant portion of users or for the development process itself. - Impact: + - A P0 bug is a catastrophic failure that demands immediate attention. + - To be a P0 it means almost all users are running into this issue and it is blocking users from being able to use the product. + - You would see this in the form of many comments from different developers on the bug. + - It represents a complete showstopper for a significant portion of users or for the development process itself. + Impact: - Blocks development or testing for the entire team. - Major security vulnerability that could compromise user data or system integrity. - Causes data loss or corruption with no workaround. @@ -172,15 +176,17 @@ jobs: Qualifier: Is the main function of the software broken? Example: The gemini auth login command fails with an unrecoverable error, preventing any user from authenticating and using the rest of the CLI. P1: High - - A P1 bug is a serious issue that significantly degrades the user experience or impacts a core feature. While not a complete blocker, it's a major problem that needs a fast resolution. - - Feature requests are almost never P1. + - A P1 bug is a serious issue that significantly degrades the user experience or impacts a core feature. + - While not a complete blocker, it's a major problem that needs a fast resolution. Feature requests are almost never P1. + - Once again this would be affecting many users. + - You would see this in the form of comments from different developers on the bug. Impact: - A core feature is broken or behaving incorrectly for a large number of users or large number of use cases. - Review the bug details and comments to try figure out if this issue affects a large set of use cases or if it's a narrow set of use cases. - Severe performance degradation making the application frustratingly slow. - No straightforward workaround exists, or the workaround is difficult and non-obvious. Qualifier: Is a key feature unusable or giving very wrong results? - Example: The gemini -p "..." command consistently returns a malformed JSON response or an empty result, making the CLI's primary generation feature unreliable. + Example: Gemini CLI enters a loop when making read-many-files tool call. I am unable to break out of the loop and gemini doesn't follow instructions subsequently. P2: Medium - A P2 bug is a moderately impactful issue. It's a noticeable problem but doesn't prevent the use of the software's main functionality. Impact: