support issue_comment, label and workflow_dispatch triggers for issue…

[JeromeJu]

This commit adds supports for all needed triggers for issue triage workflows.

Co-authored-by: aliciatang07 [email protected]

[jerop]

• Please add docs updates: https://github.com/google-gemini/gemini-cli-action/blob/main/docs/issue-triage.md
• Also update the workflow in our repo so we can dogfood this ourselves

[jerop]

thanks for addressing previous feedback

[gemini-cli]

📋 Review Summary

This pull request significantly enhances the flexibility of the issue triage workflow by adding support for new trigger mechanisms. The changes introduce issue_comment and workflow_dispatch triggers, allowing for manual and on-demand triage, which is a valuable addition. The implementation is solid, with appropriate security checks and corresponding updates to documentation and examples.

🔍 General Feedback

• The new triggers are a great feature, making the triage process much more versatile and user-friendly for repository maintainers.
• The security check on author_association for the issue_comment trigger is an excellent and crucial addition, ensuring that only authorized users can trigger the triage action.
• It's great to see that the documentation and example workflow were updated in lockstep with the functional changes.

🟡 High

High Priority Issues

• File: docs/issue-triage.md:14 - The Mermaid diagram has a small logical flaw. The new trigger D[Issue Comment with '@gemini-cli /triage' Created] correctly points to E[Get Issue Details], but the existing triggers A, B, and C should also point to E, not D. The diagram implies that an issue comment is a necessary step for all trigger types. Please adjust the diagram to have all four trigger nodes point to the E[Get Issue Details] step.
• File: docs/issue-triage.md:32 - The updated description of "Real-Time Triage" is a bit confusing. It could be misinterpreted as an issue comment being created automatically when an issue is opened. I recommend rephrasing for clarity, for example: "1. Real-Time Triage: A GitHub Actions workflow is triggered when a new issue is opened or reopened, when an authorized user creates a comment containing @gemini-cli /triage, or when a maintainer manually dispatches the triage event. This workflow uses the Gemini CLI to analyze the issue and apply the most appropriate labels, providing immediate feedback and categorization."

✅ Highlights

• The if condition in the workflow files is well-constructed, cleanly handling the logic for the different event types.
• Proactively including a security check for the issue_comment trigger demonstrates a strong consideration for secure design patterns.

[jerop]

@gemini-cli /review

[gemini-cli]

📋 Review Summary

This PR enhances the issue triage workflow by adding support for issue_comment and workflow_dispatch triggers. The changes are well-implemented, including a security check to ensure only authorized users can trigger the workflow via issue comments. The documentation has been updated to reflect these new capabilities.

🔍 General Feedback

• The addition of the issue_comment and workflow_dispatch triggers significantly improves the flexibility and usability of the issue triage workflow.
• The security check on the issue_comment trigger is a great example of building secure workflows.
• The documentation has been updated clearly and accurately.

✅ Highlights

• Secure Implementation: The check for author_association on the issue_comment trigger is a commendable security practice, preventing unauthorized or malicious use of the action.
• Improved Flexibility: The new triggers provide more ways to triage issues, making the workflow more powerful for maintainers.
• Clear Documentation: The updated documentation, including the Mermaid diagram, clearly explains the new functionality.

[JeromeJu]

The graph update should be correct despite the comment from the review