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 in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported 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 or fill out our survey to provide feedback.

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.

packages/library/cozy-lib/templates/_network.tpl (1)

5-14: Verify the logic implementation matches PR objectives.

The function correctly implements the autodetection logic: when robotlb is NOT present in the enabled components, it returns true to disable load balancer node ports. This aligns with the PR objective of allocating node ports only when RobotLB is enabled.

However, consider adding error handling for edge cases:

 {{- define "cozy-lib.network.disableLoadBalancerNodePorts" }}
 {{-   include "cozy-lib.loadCozyConfig" (list "" .) }}
 {{-   $cozyConfig := index . 1 "cozyConfig" }}
 {{-   if not $cozyConfig }}
 {{-     include "cozy-lib.network.defaultDisableLoadBalancerNodePorts" . }}
 {{-   else }}
-{{-     $enabledComponents := splitList "," ((index $cozyConfig.data "bundle-enable") | default "") }}
+{{-     $bundleEnable := index $cozyConfig.data "bundle-enable" | default "" }}
+{{-     $enabledComponents := splitList "," $bundleEnable }}
 {{-     not (has "robotlb" $enabledComponents) }}
 {{-   end }}
 {{- end }}

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

Learnt from: lllamnyp
PR: cozystack/cozystack#1233
File: packages/system/hetzner-robotlb/charts/robotlb/templates/deployment.yaml:33-35
Timestamp: 2025-07-23T09:15:09.624Z
Learning: The `./charts/robotlb/` directory in the hetzner-robotlb package contains vendored code, and the team generally avoids modifying vendored code to maintain clean separation from upstream dependencies.

packages/apps/virtual-machine/templates/service.yaml (1)

16-18: Same whitespace-trim caveat as noted in tcp-balancer template – consider dropping the - after {{ for safer, explicit indentation.

packages/apps/redis/templates/service.yaml (1)

14-16: Whitespace-trim note duplicated from earlier comment – consider {{ if …}} instead of {{- if …}}.

packages/apps/vm-instance/templates/service.yaml (1)

16-18: Whitespace-trim note duplicated from earlier comment – consider {{ if …}} instead of {{- if …}}.

packages/apps/tcp-balancer/templates/service.yaml (1)

13-15: Whitespace-trim in {{- if …}} may accidentally drop YAML indentation
Because the opening tag uses {{-, Helm trims the four leading spaces, so the rendered block becomes:

  externalTrafficPolicy: Local
allocateLoadBalancerNodePorts: false

Indentation is still valid in this template (the allocate… line keeps the required 2-space indent), but a future copy-paste with a different indent level could silently break the YAML. Switching to a non-trimming opening tag keeps the guard‐indent explicit and safer:

-    {{- if (include "cozy-lib.network.disableLoadBalancerNodePorts" $ | fromYaml) }}
+    {{ if (include "cozy-lib.network.disableLoadBalancerNodePorts" $ | fromYaml) }}

packages/apps/ferretdb/templates/external-svc.yaml (1)

11-13: Repeated snippet suggests extracting a shared partial
The three-line conditional block disabling node-ports now appears in 7 service templates. A small helper partial (e.g. cozy-lib.service.allocateNodePorts) would avoid duplication and guarantee future fixes land everywhere.

No immediate action required for this PR, just a maintainability hint.

packages/apps/http-cache/templates/haproxy/service.yaml (1)

13-15: Align indentation and switch to toBool for a cleaner, safer boolean check

1. Indentation: the if/end directives are indented by four spaces while their sibling keys (type, externalTrafficPolicy) use two. After the {{- trim, Helm will emit a blank line that is purely cosmetic but keeps the template visually uneven across files. Using two-space indentation here maintains visual consistency and avoids the blank line.

2. Boolean parsing: fromYaml works, but its intent is to convert documents to structured data. For single booleans, toBool is more idiomatic and avoids edge-cases when the included helper ever returns an empty string.

Suggested change:

-    {{- if (include "cozy-lib.network.disableLoadBalancerNodePorts" $ | fromYaml) }}
-  allocateLoadBalancerNodePorts: false
-    {{- end }}
+  {{- if (include "cozy-lib.network.disableLoadBalancerNodePorts" $ | toBool) }}
+  allocateLoadBalancerNodePorts: false
+  {{- end }}

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

Learnt from: lllamnyp
PR: cozystack/cozystack#1233
File: packages/system/hetzner-robotlb/charts/robotlb/templates/deployment.yaml:33-35
Timestamp: 2025-07-23T09:15:09.658Z
Learning: The `./charts/robotlb/` directory in the hetzner-robotlb package contains vendored code, and the team generally avoids modifying vendored code to maintain clean separation from upstream dependencies.