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

docs/api/ctx.md (3)

2051-2054: Fix MDN link and tighten wording around Link header(s).

Current MDN URL points to a non-existent “Reference” path and “headers” is redundant here.

-[`Link` headers](https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/Link)
+[`Link` header](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Link)
- before the final response. This allows the browser to start preloading
- resources while the server prepares the full response.
+ before the final response. This lets browsers start preloading resources
+ while the server prepares the final response.

---

2055-2058: Rephrase protocol support caveat (HTTP/1.1 can carry 103 but support is inconsistent).

“Requires HTTP/2 or newer” is too strong. 103 can technically be sent over HTTP/1.1; the real pitfall is client/CDN/proxy support. Suggest a more accurate caution.

-:::caution
-This feature requires HTTP/2 or newer. Some legacy HTTP/1.1 clients may not
-understand or may misbehave when receiving early hints.
-:::
+:::caution
+Early Hints are most effective over HTTP/2 or HTTP/3. While the 103 status can
+be sent over HTTP/1.1, many clients and intermediaries ignore or mishandle it.
+Validate support in your clients, CDN, and reverse proxy before enabling in production.
+:::

---

2064-2072: Enrich the example with multiple hints and crossorigin; optionally show header-based flow.

Demonstrate typical real-world preloads (script + CSS) and include crossorigin when appropriate.

-hints := []string{"<https://cdn.com/app.js>; rel=preload; as=script"}
+hints := []string{
+  "<https://cdn.com/app.js>; rel=preload; as=script; crossorigin",
+  "<https://cdn.com/app.css>; rel=preload; as=style",
+}
 app.Get("/early", func(c fiber.Ctx) error {
   if err := c.SendEarlyHints(hints); err != nil {
     return err
   }
   return c.SendString("done")
 })

If the function instead forwards already-set Link headers, add this alternative example after verification:

// Alternative: pre-set Link headers then call SendEarlyHints
app.Get("/early", func(c fiber.Ctx) error {
  c.Append("Link", "<https://cdn.com/app.js>; rel=preload; as=script; crossorigin")
  c.Append("Link", "<https://cdn.com/app.css>; rel=preload; as=style")
  if err := c.SendEarlyHints(nil); err != nil {
    return err
  }
  return c.SendString("done")
})

docs/whats_new.md (2)

467-469: Link the new method to the API reference for discoverability.

Add a direct link to the API section you added in ctx.md.

-- **SendEarlyHints**: Sends `103 Early Hints` with `Link` headers so browsers can preload resources while the final response is being prepared.
+- **SendEarlyHints**: Sends `103 Early Hints` with `Link` headers so browsers can preload resources while the final response is being prepared. See [Ctx.SendEarlyHints](./api/ctx.md#sendearlyhints).

---

509-524: Add references and a brief protocol support note.

Provide a standards link and clarify HTTP/1.1 behavior to match the API page caution.

-`SendEarlyHints` enables servers to emit [`103 Early Hints`](https://developer.chrome.com/docs/web-platform/early-hints) so
+`SendEarlyHints` enables servers to emit [`103 Early Hints`](https://developer.chrome.com/docs/web-platform/early-hints) ([RFC 8297])
+so
@@
-Older HTTP/1.1 clients may ignore these interim responses or handle them inconsistently.
+Older HTTP/1.1 clients and some intermediaries may ignore or mishandle these interim responses; validate support in clients, CDN, and reverse proxies.

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

💡 Knowledge Base configuration:

• MCP integration is disabled by default for public repositories
• Jira integration is disabled by default for public repositories
• Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

docs/whats_new.md (1)

509-512: I’ve initiated a search for the SendEarlyHints implementation to confirm whether it uses only the provided slice or forwards preset headers. I’ll update you once we have the findings.