Skip to content

Conversation

@joshlf
Copy link
Member

@joshlf joshlf commented Feb 10, 2026


Latest Update: v3 — Compare vs v2

📚 Full Patch History

Links show the diff between the row version and the column version.

Version v2 v1 Base
v3 vs v2 vs v1 vs Base
v2 vs v1 vs Base
v1 vs Base
⬇️ Download this PR

Branch

git fetch origin refs/heads/GI7PO52I2CB3PQQC425CDLSKBPLNCSPM3 && git checkout -b pr-GI7PO52I2CB3PQQC425CDLSKBPLNCSPM3 FETCH_HEAD

Checkout

git fetch origin refs/heads/GI7PO52I2CB3PQQC425CDLSKBPLNCSPM3 && git checkout FETCH_HEAD

Cherry Pick

git fetch origin refs/heads/GI7PO52I2CB3PQQC425CDLSKBPLNCSPM3 && git cherry-pick FETCH_HEAD

Pull

git pull origin refs/heads/GI7PO52I2CB3PQQC425CDLSKBPLNCSPM3

Stacked PRs enabled by GHerrit.

gherrit-pr-id: G9611b9a3ca0254d8ba488d591e6a21980cca3d29
gherrit-pr-id: Gb7f1abf97eed8a035dbcaf7b0363b5890baaec05
gherrit-pr-id: Gdc72294eb3c40c4afa61ea6e8f965ba310cd22ef
gherrit-pr-id: G48b27aa33306f1b4bae6f7996a68c1a1869d0a9a
gherrit-pr-id: G93b59d9ea956b7e2e06b2e91c45dea803a391801
gherrit-pr-id: G2f234da34d5c9cd516c08526882baaee631fe7d2
gherrit-pr-id: G3220747e90b678c598c506be49219a8f75118988
gherrit-pr-id: Gbeb9a3b076d434abb7e0a799fdb18c4ad9fb87a2
gherrit-pr-id: G833f306c404eb4d4f3d920a8b169a5570b3806a4
Previously, we stored the shadow crate in `target/hermes_shadow_<hash>`.
Now we store it in `target/hermes/<hash>/shadow`. This allows us to
store other build artifacts in `target/hermes/<hash>` but outside of
`/shadow` to avoid polluting the shadow copy.

gherrit-pr-id: G7f8abd90b628d02a6fdc01985535eef50509312e
gherrit-pr-id: Ge1bd84b5d857e18e3668e809844c6d73b808a020
gherrit-pr-id: G60bb1cd41a5fade3144a05f2bdafb2a670059e03
gherrit-pr-id: G3db3762006cf6333a7112b668f747072f8bb477b
@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello @joshlf, 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 introduces a minor code cleanup within the hermes tool, specifically in the transform::apply_edits function. The change refactors a byte comparison condition to utilize Rust's matches! macro, enhancing code readability and conciseness without altering the function's behavior.

Highlights

  • Code Refactoring: Replaced a boolean && expression with the more idiomatic matches! macro for byte comparison within the apply_edits function, improving code readability.

🧠 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
  • tools/hermes/src/transform.rs
    • Refactored byte comparison in apply_edits to use the matches! macro for improved readability.
Activity
  • No specific 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
Contributor

@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 a minor but valuable cleanup in the apply_edits function. The use of the matches! macro instead of a chain of != comparisons is more idiomatic in Rust and improves the readability of the code. The change is correct and has no performance or security implications. This is a good refinement.

@codecov-commenter
Copy link

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 91.87%. Comparing base (34f4c95) to head (bff925c).

Additional details and impacted files
@@                            Coverage Diff                             @@
##           Gc48bae5a713c0931a406c162369f4a30ddc1f2b3    #3025   +/-   ##
==========================================================================
  Coverage                                      91.87%   91.87%           
==========================================================================
  Files                                             20       20           
  Lines                                           6057     6057           
==========================================================================
  Hits                                            5565     5565           
  Misses                                           492      492           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

… errors

* Normalize paths between integration runner's
* Map cargo's absolute shadow output paths reliably by replacing temporary workspaces
* Inject  effectively through Charon driver
* Remove diagnostic prints and fallback to deterministic string-replacement for verification assertions
* Fix mapping of  outputs to use robust non-spanning fallbacks
* Take responsibility for all terminal UI

gherrit-pr-id: Gd1a7f9c4436f266d37e83ebc2310f5a99a73d24d
gherrit-pr-id: GI7PO52I2CB3PQQC425CDLSKBPLNCSPM3
@joshlf joshlf force-pushed the GI7PO52I2CB3PQQC425CDLSKBPLNCSPM3 branch from bff925c to aa81e5b Compare February 10, 2026 20:31
@joshlf joshlf changed the base branch from Gc48bae5a713c0931a406c162369f4a30ddc1f2b3 to Gd1a7f9c4436f266d37e83ebc2310f5a99a73d24d February 10, 2026 20:31
@joshlf joshlf force-pushed the Gd1a7f9c4436f266d37e83ebc2310f5a99a73d24d branch from 8771c47 to d46c4e1 Compare February 10, 2026 23:18
@joshlf
Copy link
Member Author

joshlf commented Feb 10, 2026

Squashed into #3004

@joshlf joshlf closed this Feb 10, 2026
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