Skip to content

5.6.20#1726

Merged
arhtudormorar merged 2 commits intomainfrom
development
Mar 10, 2026
Merged

5.6.20#1726
arhtudormorar merged 2 commits intomainfrom
development

Conversation

@arhtudormorar
Copy link
Contributor

No description provided.

@arhtudormorar arhtudormorar merged commit 5d34060 into main Mar 10, 2026
3 checks passed
@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 primarily updates the project to version 5.6.20 and introduces a new feature that provides more control over transaction signing by allowing guardian checks to be optionally skipped. This enhancement offers flexibility for scenarios where guardian intervention is not required or desired during the transaction signing process.

Highlights

  • Guardian Checks: Introduced an optional skipGuardian flag in the signTransactions function, allowing guardian checks to be bypassed when signing transactions.

🧠 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
  • CHANGELOG.md
    • Added a new entry for version 5.6.20, documenting the addition of the skipGuardian option in the signTransactions function.
  • package.json
    • Updated the package version from 5.6.19 to 5.6.20.
  • src/providers/strategies/helpers/signTransactions/signTransactions.ts
    • Implemented conditional logic to skip guardian checks based on the options?.skipGuardian flag within the signTransactions function.
Activity
  • No human activity has been recorded for this pull request yet.
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 introduces an option to skip guardian checks when signing transactions and bumps the package version to 5.6.20. The implementation is correct. I've added one suggestion to refactor a small piece of duplicated logic into a helper function to improve code maintainability.

Comment on lines +59 to +61
const optionallyGuardedTransactions = options?.skipGuardian
? signedTransactions
: await guardTransactions(signedTransactions);

Choose a reason for hiding this comment

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

medium

This logic for conditionally applying guardian checks is duplicated later in the file (lines 253-255). To improve maintainability and reduce code duplication, consider extracting this logic into a local helper function within signTransactions.

For example:

const applyGuardian = (txs: Transaction[]) =>
  options?.skipGuardian ? Promise.resolve(txs) : guardTransactions(txs);

Then you could simplify this to:

const optionallyGuardedTransactions = await applyGuardian(signedTransactions);

And apply the same simplification on line 253 for finalizedTransactions.

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.

3 participants