-
Notifications
You must be signed in to change notification settings - Fork 70
chore: Update auto triage guidelines #3882
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
📋 Review Summary
This PR updates the issue triage workflow to use a new label format and adds more specific guidelines for handling issue priorities. The changes are clear and improve the automation. I've left one minor comment regarding a typo.
🔍 General Feedback
- The changes are well-documented within the workflow file itself.
- The new guidelines for handling high-priority issues and preserving existing labels are good additions.
|
There is a problem with the Gemini CLI PR review. Please check the action logs for details. |
|
@gemini-cli /review |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
📋 Review Summary
This pull request updates the guidelines for the Gemini CLI's automated issue triage workflows. The changes aim to standardize the labeling process and clarify the handling of high-priority issues.
🔍 General Feedback
The overall direction of the changes is good, particularly the move to a more structured labeling system (type: and priority:). However, there is a significant contradiction in the new instructions that needs to be addressed. The guidelines instruct the AI to add a comment for high-priority issues, while also stating that it should not add any comments. This conflict needs to be resolved for the workflows to function as intended.
|
|



No description provided.