chore: rename online RL examples to make it more attractive

[garrett4wade]

No description provided.

[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 focuses on improving the presentation of the online reinforcement learning examples by restructuring their directory and updating associated references. The primary goal is to make these examples more intuitive and appealing to users, ensuring that all documentation and scripts correctly point to the new location.

Highlights

• Directory Renaming: The examples/online_rl directory has been renamed to examples/openclaw to enhance clarity and attractiveness for the reinforcement learning examples.
• Path Updates: All internal file references within the renamed files, such as those in README.md and demo_lifecycle.py, have been updated to reflect the new examples/openclaw path.

🧠 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

• examples/openclaw/README.md
  • Renamed from examples/online_rl/zeroclaw.md.
  • Updated references to train.py and config.yaml to use the new examples/openclaw path.
• examples/openclaw/_fmt.py
  • Renamed from examples/online_rl/_fmt.py.
• examples/openclaw/config.yaml
  • Renamed from examples/online_rl/config.yaml.
• examples/openclaw/demo_lifecycle.py
  • Renamed from examples/online_rl/demo_lifecycle.py.
  • Updated the reference to train.py to use the new examples/openclaw path.
• examples/openclaw/set_reward.py
  • Renamed from examples/online_rl/set_reward.py.
• examples/openclaw/start_session.py
  • Renamed from examples/online_rl/start_session.py.
• examples/openclaw/train.py
  • Renamed from examples/online_rl/train.py.

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

[gemini-code-assist]

Code Review

This pull request renames the online_rl example directory to openclaw and updates all relevant file paths. No security vulnerabilities were found. The changes are mostly correct, with a suggestion to update the title in the new README.md file for consistency with the new directory name, which will improve clarity for users.