docs: Update example of using GlobalTrajectoryMiddleware to specify what to logs

[yuit]

Which issue(s) does this pull-request address?

Example is out-of-date. Examples incorrectly use target parameter to specify what to include in trajectory.

Description

Update the example to use included instead of target

Checklist

General

• I have read the appropriate contributor guide: Python
  / TypeScript
• I have signed off on my commit: Python instructions / TypeScript instructions
• [x ] Commit messages and PR title follow conventional commits
• Appropriate label(s) added to PR: Python for Python changes, TypeScript for TypeScript changes

Code quality checks

• Code quality checks pass: mise check (mise fix to auto-fix)

Testing

• Unit tests pass: mise test:unit
• E2E tests pass: mise test:e2e
• Tests are included (for bug fixes or new features)

Documentation

• Documentation is updated
• Embedme embeds code examples in docs. To update after edits, run: Python mise docs:fix

[gemini-code-assist]

Summary of Changes

Hello, I'm Gemini Code Assist¹! 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 addresses an out-of-date example in the documentation for GlobalTrajectoryMiddleware. The change ensures that the documentation accurately reflects the current API by replacing the target parameter with included for specifying logging configurations, thereby improving clarity and correctness for users.

Highlights

• Documentation Update: The example for GlobalTrajectoryMiddleware in the documentation has been updated to use the correct parameter included instead of the outdated target when specifying what to log.

🧠 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.

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. ↩

[gemini-code-assist]

Code Review

This pull request corrects an example in the documentation for GlobalTrajectoryMiddleware. The target parameter was being used to specify which classes to log, which was incorrect. This has been updated to use the included parameter, which is the correct way to filter logged classes. This change makes the documentation consistent with the implementation, which will help prevent user confusion.