feat: add useGeminiReview hook with comment cleanup

[rm-hull]

Introduces a specialized hook to handle Gemini code reviews. This ensures a cleaner pull request timeline by removing previous gemini-code-assist comments before posting a new review request.

• Encapsulates the review logic away from the button component.
• Automatically deletes existing assistant comments.
• Invalidates the open-prs query state upon successful completion.

sequenceDiagram
    participant UI as GeminiReviewButton
    participant Hook as useGeminiReview
    participant API as GitHub API
    UI->>Hook: mutate()
    Hook->>API: listComments()
    API-->>Hook: comments
    Note over Hook: Filter "gemini-code-assist" comments
    loop Each existing comment
        Hook->>API: deleteComment()
    end
    Hook->>API: createComment("/gemini review")
    Hook->>Hook: invalidate open-prs

Loading

[coveralls]

Pull Request Test Coverage Report for Build 23121634691

Details

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 52.381%

---

Totals
Change from base Build 23051549628:	0.0%
Covered Lines:	30
Relevant Lines:	59

---

💛 - Coveralls

[rm-hull]

/gemini review

[gemini-code-assist]

Code Review

This pull request introduces a new useGeminiReview hook, which is a great improvement as it encapsulates the logic for handling Gemini code reviews and cleans up the component code. The implementation is solid, but I've identified a couple of opportunities to improve performance by parallelizing API calls within the new hook. My suggestions aim to make the process of cleaning up old comments and fetching data more efficient.

[gemini-code-assist]

The two paginate calls to fetch issue comments and review comments are executed sequentially. Since they are independent, you can run them in parallel using Promise.all to improve performance by reducing the total wait time for data fetching.

Suggested change

	const comments = await octokit.paginate(octokit.issues.listComments, {
	owner,
	repo,
	issue_number: pull_number,
	per_page: 100,
	});
	const geminiComments = comments.filter((c) => c.user?.login === GEMINI_USER_LOGIN);
	const reviewComments = await octokit.paginate(octokit.pulls.listReviewComments, {
	owner,
	repo,
	pull_number,
	per_page: 100,
	});
	const geminiReviewComments = reviewComments.filter((c) => c.user?.login === GEMINI_USER_LOGIN);
	const [comments, reviewComments] = await Promise.all([
	octokit.paginate(octokit.issues.listComments, {
	owner,
	repo,
	issue_number: pull_number,
	per_page: 100,
	}),
	octokit.paginate(octokit.pulls.listReviewComments, {
	owner,
	repo,
	pull_number,
	per_page: 100,
	}),
	]);
	const geminiComments = comments.filter((c) => c.user?.login === GEMINI_USER_LOGIN);
	const geminiReviewComments = reviewComments.filter((c) => c.user?.login === GEMINI_USER_LOGIN);

[gemini-code-assist]

The loops for deleting comments run sequentially, which can be slow if there are many comments to delete. You can significantly improve performance by running these deletion requests in parallel using Promise.all. This also makes the code more concise and handles errors for individual deletions gracefully without needing explicit try...catch blocks inside loops.

      const deletionPromises = [
        ...geminiComments.map((comment) =>
          octokit.issues.deleteComment({ owner, repo, comment_id: comment.id }).catch((e) => {
            console.error(`Failed to delete issue comment ${comment.id}`, e);
          }),
        ),
        ...geminiReviewComments.map((comment) =>
          octokit.pulls.deleteReviewComment({ owner, repo, comment_id: comment.id }).catch((e) => {
            console.error(`Failed to delete review comment ${comment.id}`, e);
          }),
        ),
      ];

      await Promise.all(deletionPromises);