Skip to content

Add typedargs gem specification file#477

Merged
bovi merged 1 commit intomruby:masterfrom
Asmod4n:patch-38
Feb 24, 2026
Merged

Add typedargs gem specification file#477
bovi merged 1 commit intomruby:masterfrom
Asmod4n:patch-38

Conversation

@Asmod4n
Copy link
Contributor

@Asmod4n Asmod4n commented Feb 23, 2026

Hope you are happy there is no mruby prefix, since its a hybrid gem for mruby and ruby.

@Asmod4n Asmod4n requested a review from matz as a code owner February 23, 2026 14:32
@gemini-code-assist
Copy link

Summary of Changes

Hello @Asmod4n, 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 establishes the foundational metadata for the typedargs project by adding its gem specification file. This critical addition enables the proper packaging, distribution, and installation of the typedargs gem, ensuring its availability and discoverability for developers utilizing both mruby and standard Ruby runtimes.

Highlights

  • Gem Specification File Added: A new file, "typedargs.gem", has been introduced to define the metadata for the typedargs gem.
  • Hybrid Gem Support: The gem specification explicitly supports typedargs as a hybrid gem, compatible with both mruby and Ruby environments, as noted in the pull request description.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Changelog
  • typedargs.gem
    • Added the gem specification file, including metadata such as name, description, author, repository, and license.
Activity
  • Asmod4n opened this pull request, noting that the gem is designed as a hybrid for both mruby and Ruby, which influenced the naming convention.
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.

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 adds the typedargs gem specification. The submission is well-formed, but it deviates from the naming conventions outlined in the repository's README.md file. Specifically, the gem name is missing the required mruby- prefix. I have left a comment with a suggestion to correct this for consistency.

@bovi bovi merged commit 704a849 into mruby:master Feb 24, 2026
3 checks passed
@bovi
Copy link
Member

bovi commented Feb 24, 2026

maybe it would be meaningful to start having an additional structure (directories) to start bringing some structure in all the gems here. but I'm afraid it might break some downstream tooling.

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