Skip to content

Conversation

@JacksonMei
Copy link
Collaborator

No description provided.

@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello @JacksonMei, 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 significantly enhances the documentation and command-line interface for environment management. It clarifies the distinction between temporary 'Environment Instances' and persistent 'Environment Services', providing comprehensive guides on their usage and management. The changes also update the underlying configuration schema to support the new service deployment capabilities, offering more granular control over resource allocation and persistence for different environment types.

Highlights

  • New Environment Concepts: Introduced and documented two distinct deployment modes: 'Environment Instance' for temporary, on-demand compute and 'Environment Service' for long-running, persistent applications. This includes their purpose, key characteristics, use cases, and a detailed comparison matrix.
  • Enhanced CLI Commands: Added new CLI command groups: aenv instance for managing the full lifecycle of temporary environment instances (create, list, get, delete) and aenv service for managing persistent environment services (create, list, get, delete, update). The legacy aenv instances command is now noted as such.
  • Updated Configuration Schema: Modified the deployConfig in config.json to support new parameters like ephemeralStorage and environmentVariables. A new nested service block was added to configure service-specific deployment options such as replicas, port, and persistent storage settings (enableStorage, storageName, storageSize, mountPath).

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

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 provides a comprehensive update to the CLI documentation, introducing the new instance and service commands and their configurations. The documentation is well-structured and detailed. I've identified a few minor areas for improvement to enhance clarity and consistency, including a table formatting issue, a potentially confusing configuration example, and inconsistent product naming. My suggestions aim to make the documentation even more user-friendly.

| `--ttl` | `-t` | Time to live (e.g., 30m, 1h) | 30m |
| `--env` | `-e` | Environment variables (KEY=VALUE) | - |
| `--arg` | `-a` | Command line arguments | - |
| `--system-url` | | AEnv system URL | from env/config |
Copy link
Contributor

Choose a reason for hiding this comment

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

medium

The documentation appears to use AEnvironment, AEnv, Aenv, and aenv inconsistently. For clarity and consistency, I recommend standardizing the naming across all documentation. A good approach would be to use AEnvironment for the project name and aenv for the CLI tool. In this line, AEnv could be changed to aenv if it refers to the CLI, or AEnvironment if it refers to the overall system.

+------------------+-------------+---------+--------+----------+----------+--------------+----------------------+
| Service ID | Environment | Owner | Status | Replicas | Storage | Service URL | Created At |
+==================+=============+=========+========+==========+==========+==============+======================+
| myapp-svc-abc123 | myapp@1.0.0 | user1 | Ready | 3/3 | myapp-pvc| myapp-svc... | 2026-01-19T10:30:00Z |
Copy link
Contributor

Choose a reason for hiding this comment

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

medium

The formatting of this table row appears to be broken due to a missing space around a pipe (|) character between the 'Storage' and 'Service URL' columns. This will likely cause rendering issues in the markdown table.

Suggested change
| myapp-svc-abc123 | myapp@1.0.0 | user1 | Ready | 3/3 | myapp-pvc| myapp-svc... | 2026-01-19T10:30:00Z |
| myapp-svc-abc123 | myapp@1.0.0 | user1 | Ready | 3/3 | myapp-pvc | myapp-svc... | 2026-01-19T10:30:00Z |

"os": "linux",
"ephemeralStorage": "5Gi",
"imagePrefix": "registry.example.com/envs",
"podTemplate": "",
Copy link
Contributor

Choose a reason for hiding this comment

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

medium

The example shows podTemplate as an empty string, while the description on line 133 states it defaults to "singleContainer". This could be confusing for users. To improve clarity, it would be better if the example explicitly showed the default value.

Suggested change
"podTemplate": "",
"podTemplate": "singleContainer",

JacksonMei and others added 2 commits January 19, 2026 11:09
- Add comprehensive documentation for `aenv instance` and `aenv service` commands in cli.md
- Update config.json examples to match official template structure
- Add detailed field descriptions for deployConfig.service configuration
- Add "Environment Instance vs Environment Service" comparison in concepts.md
- Mark optional fields (imagePrefix, podTemplate) explicitly
- Fix markdownlint duplicate heading issue

Key updates:
1. CLI documentation (docs/guide/cli.md):
   - Complete documentation for instance subcommands (create, list, get, delete)
   - Complete documentation for service subcommands (create, list, get, delete, update)
   - Usage examples and option descriptions for all commands

2. Environment configuration (docs/guide/environments.md):
   - Updated config.json examples to match official template defaults
   - Added deployConfig.service fields documentation
   - Separated core and optional deployment parameters
   - Added extended configuration examples

3. Core concepts (docs/getting_started/concepts.md):
   - Added detailed comparison between Instance and Service
   - Added use cases and management commands
   - Added comparison matrix with 9 dimensions
   - Added guidance on when to use which deployment mode

Co-Authored-By: Claude <noreply@anthropic.com>
Copy link
Collaborator

@kangoal kangoal left a comment

Choose a reason for hiding this comment

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

LGTM

@kangoal kangoal merged commit aa84268 into main Jan 19, 2026
1 check passed
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