Skip to content

Automate bug triaging with Gemini CLI - #4

Merged
sadym-chromium merged 1 commit into
mainfrom
gemini
Dec 2, 2025
Merged

sadym-chromium merged 1 commit into
mainfrom
gemini

Conversation

@sadym-chromium

@sadym-chromium sadym-chromium commented Dec 2, 2025

Copy link
Copy Markdown
Collaborator

Add instructions for gemini + readme for developers.

Example of a generated test: https://github.com/GoogleChromeLabs/chromedriver-bug-repro-templates/blob/42323156/macos-selenium-mochajs/test.js

@sadym-chromium
sadym-chromium requested a review from alexnj December 2, 2025 14:19
@sadym-chromium
sadym-chromium merged commit b18dfe0 into main Dec 2, 2025
3 checks passed
@@ -0,0 +1,13 @@
# Gemini CLI Prompt for ChromeDriver Bug Triage

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we should move this to repo's top level, with the prompt modified to pick appropriate template for repro based on technology/language/repro steps stated in the issue. It should probably be modified to also modify the github action to spin up the right environment, if one is not available.


**Workflow:**

1. Read the bug description for the provided bug ID to understand the reproduction steps.

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This might not work for external users?


### Prerequisits

Consult internal documentation for exact MCP servers required to access Buganizer.

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Qualify this as for Google internal users?

@sadym-chromium
sadym-chromium deleted the gemini branch December 3, 2025 21:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants