Automate bug triaging with Gemini CLI #4
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,13 @@ | ||
| # Gemini CLI Prompt for ChromeDriver Bug Triage | ||
|
|
||
| Your task is to triage a ChromeDriver bug report using this pre-configured bug reproduction template. The goal is to confirm the bug's presence by writing a test that is expected to fail. | ||
|
|
||
| **Bug to Triage:** `b/<BUG_ID>` (Please provide the actual bug ID in your prompt) | ||
|
|
||
| **Workflow:** | ||
|
|
||
| 1. Read the bug description for the provided bug ID to understand the reproduction steps. | ||
|
Collaborator
There was a problem hiding this comment. This might not work for external users? |
||
| 2. Modify the `test.js` file in the current directory to add a new test case that attempts to reproduce this bug. | ||
| 3. **Crucially, the test must be written to fail if the bug exists.** The assertion in the test should check for the correct behavior, which will fail if the bug is present. | ||
| 4. The new test code must be thoroughly commented, explaining the reproduction steps, what the test is doing, and why it is expected to fail in the presence of the bug. **Specifically, justify the `expected` value in the assertion using details from the bug description and, if relevant, the WebDriver specification.** | ||
| 5. After adding the test, run the test suite to confirm that the new test fails as expected, which successfully reproduces the bug. | ||
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
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.