Skip to content

Conversation

@sunithvs
Copy link
Owner

@sunithvs sunithvs commented Aug 5, 2025

Summary

Description

Motivation and Context

How has this been tested?

Screenshots (if appropriate):

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist:

  • My code follows the code style of this project.
  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.

@vercel
Copy link
Contributor

vercel bot commented Aug 5, 2025

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
devb-io ❌ Failed (Inspect) Aug 5, 2025 5:24am

@sunithvs sunithvs merged commit 7d95e97 into main Aug 5, 2025
1 of 3 checks passed
Copy link

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

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

Summary of Changes

Hello @sunithvs, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

I've addressed a bug where the links for 'Buy Me a Coffee' and 'GitHub' were inadvertently swapped within the support modal. This PR ensures that clicking the 'Fuel Code Card' now correctly navigates to the 'Buy Me a Coffee' page, and the 'Star GitHub Card' correctly directs users to the GitHub repository.

Highlights

  • Link Correction: Fuel Code Card: The 'Fuel Code Card' in the support modal now correctly links to the DEVB_BUY_ME_A_COFFEE_LINK.
  • Link Correction: Star GitHub Card: The 'Star GitHub Card' in the support modal now correctly links to the DEVB_GITHUB_LINK.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in issue comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments or fill out our survey to provide feedback.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

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

Code Review

This pull request correctly swaps the DEVB_BUY_ME_A_COFFEE_LINK and DEVB_GITHUB_LINK constants for the 'Fuel our code' and 'Star our GitHub' cards in the support modal. This fixes a bug where the links were pointing to the wrong destinations. My review identifies an opportunity to improve the accessibility of these interactive cards. While the onClick handlers are now functionally correct, they are attached to div elements, which are not accessible to keyboard users by default. I've added comments with suggestions to ensure all users can interact with these elements.

{/* Fuel Code Card */}
<div
onClick={() => openInNewTab(DEVB_GITHUB_LINK)}
onClick={() => openInNewTab(DEVB_BUY_ME_A_COFFEE_LINK)}

Choose a reason for hiding this comment

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

medium

While the link is now correct, this onClick handler is on a div element, which is not keyboard-accessible by default. This prevents users who rely on keyboard navigation from using this feature. To make this interactive card accessible, the parent div should either be a <button> element or have role="button" and tabIndex={0} attributes.

{/* Star GitHub Card */}
<div
onClick={() => openInNewTab(DEVB_BUY_ME_A_COFFEE_LINK)}
onClick={() => openInNewTab(DEVB_GITHUB_LINK)}

Choose a reason for hiding this comment

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

medium

Similar to the other card, this onClick handler is on a non-interactive div element, making it inaccessible to keyboard users. Please consider converting the parent div to a <button> or adding role="button" and tabIndex={0} for proper accessibility.

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