Skip to content

Add more fields to README examples#330

Merged
horgh merged 2 commits intomainfrom
wstorey/docs
Mar 25, 2026
Merged

Add more fields to README examples#330
horgh merged 2 commits intomainfrom
wstorey/docs

Conversation

@horgh
Copy link
Contributor

@horgh horgh commented Mar 25, 2026

No description provided.

horgh and others added 2 commits March 25, 2026 11:14
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@gemini-code-assist
Copy link

Summary of Changes

Hello, 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!

This pull request improves the clarity and completeness of the example code snippets in the README.rst file. By incorporating additional fields for card and payment details, the examples now offer a more robust and realistic representation of the data structures, aiding users in understanding and implementing the library's features more effectively.

Highlights

  • Documentation Update: Added a 'token' field to the card details example within the README.rst file to provide a more comprehensive illustration of card data.
  • Documentation Update: Included 'is_gift' and 'has_gift_message' fields in the payment details example in README.rst, enhancing the clarity of payment object structures.
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 by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

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 pull request 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. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here.

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 updates the README.rst file to include new fields in the example JSON structures. Specifically, it adds a token field to the payment_instrument example and is_gift and has_gift_message fields to the payment example. There is no feedback to provide as no review comments were made.

Copy link

@mm-jpoole mm-jpoole left a comment

Choose a reason for hiding this comment

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

LGTM! 🥳

@horgh horgh merged commit 261b267 into main Mar 25, 2026
47 checks passed
@horgh horgh deleted the wstorey/docs branch March 25, 2026 20:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants