Skip to content

Stage - #72

Merged
evereq merged 5 commits into
stagefrom
develop
Jul 28, 2026
Merged

Stage#72
evereq merged 5 commits into
stagefrom
develop

Conversation

@evereq

@evereq evereq commented Jul 28, 2026

Copy link
Copy Markdown
Member

No description provided.

@coderabbitai

coderabbitai Bot commented Jul 28, 2026

Copy link
Copy Markdown

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 06df3a14-76c5-444d-b048-cc461bd67f8e

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch develop

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@evereq
evereq merged commit cf37d3c into stage Jul 28, 2026
9 of 11 checks passed
@codacy-production

Copy link
Copy Markdown

Not up to standards ⛔

NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.

<li>

**Check the API is reachable** — visit{" "}
<code>[https://api.ever.team/api/health](https://api.ever.team/api/health)</code>, or your own API host, and

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P2 Health endpoint renders as source

The Markdown link is nested inside <code>, so the support page displays the raw link syntax instead of a clickable health endpoint, adding friction to the troubleshooting step.

Suggested change
<code>[https://api.ever.team/api/health](https://api.ever.team/api/health)</code>, or your own API host, and
<a href="https://api.ever.team/api/health"><code>https://api.ever.team/api/health</code></a>, or your own API host, and

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!

@greptile-apps

greptile-apps Bot commented Jul 28, 2026

Copy link
Copy Markdown

Greptile Summary

This PR redesigns the documentation site and expands its support and product content.

  • Adds comprehensive Support and Ever Teams Kit documentation, styling, and sidebar integration.
  • Restyles the global navigation, search, footer, tables, responsive layouts, themes, logos, and promotional sidebar.
  • Updates GitHub Actions versions and runner selection for CodeQL and container publishing.

Confidence Score: 4/5

The PR appears safe to merge, with a non-blocking documentation formatting issue on the new support page.

The site changes are internally consistent, but the health endpoint is placed as Markdown link syntax inside a code element, causing readers to see a non-clickable source-formatted URL.

Files Needing Attention: website/docs/advanced-guide/support.mdx

T-Rex T-Rex Logs

What T-Rex did

  • Generated and linked a finding-comment-proof for the posted P1 finding.
  • Validated the contract behavior changes by comparing pre- and post-change states: promoCount became 1, sidebarMenuCount became 0, normal docs page shows normalSidebarMenuCount: 1 and a visible footer; hydration mismatches occurred after navigation with server-rendered content replaced by client rendering.

View all artifacts

T-Rex Ran code and verified through T-Rex

Important Files Changed

Filename Overview
website/docs/advanced-guide/support.mdx Adds the full support guide and channel components; one health-check URL renders as literal Markdown instead of a usable link.
website/docusaurus.config.ts Reconfigures fonts, navigation, search placement, logos, footer metadata, and table-of-contents behavior.
website/src/css/custom.css Replaces and substantially expands the site-wide visual system, responsive behavior, and light/dark theme styling.
website/src/components/SidebarPromo/index.tsx Adds a route-aware promotional sidebar for the support page.
website/src/theme/MDXComponents.tsx Wraps Markdown tables in keyboard-focusable horizontal scroll containers.
website/docs/kit/index.mdx Introduces the Ever Teams Kit overview and links it into the documentation.
.github/workflows/k8s-build.yml Updates action major versions and selects the smaller configurable Linux runner.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart LR
  Navbar[Navbar] --> Docs[Documentation]
  Navbar --> Support[Support page]
  Support --> Promo[Cloud sidebar promo]
  Docs --> Kit[Ever Teams Kit]
  Docs --> Tables[Scrollable MDX tables]
  Theme[Global theme tokens] --> Navbar
  Theme --> Support
  Theme --> Kit
  Theme --> Footer[Custom footer]
Loading

Comments Outside Diff (1)

  1. General comment

    P1 Support page causes React hydration failure

    • Bug
      • Loading the changed /advanced-guide/support page from the production build emits many React error #418 hydration mismatches followed by error #423, indicating that hydration failed and React switched the root to client rendering. The same baseline route produced no browser errors. Although the page remains visible, this discards SSR work and can cause content replacement or layout instability during startup.
    • Cause
      • The new MDX wraps Markdown content in explicit JSX <p> elements while leaving blank lines around the content, for example near website/docs/advanced-guide/support.mdx:121-128 and :132-137. The generated server HTML confirms these become an empty styled paragraph followed by a separate unstyled paragraph and another empty paragraph (<p class="heroLead_…"></p><p>…</p><p></p>), producing markup that does not agree with the client render. The pattern is repeated elsewhere in the page.
    • Fix
      • Do not place Markdown blocks separated by blank lines inside explicit JSX <p> wrappers. Keep the text inline with the opening and closing tag, or use a <div> wrapper and style its generated paragraph. Rebuild and verify that the production Support route loads with no onRecoverableError messages.

    T-Rex Ran code and verified through T-Rex

Reviews (1): Last reviewed commit: "Merge pull request #71 from ever-co/feat..." | Re-trigger Greptile

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.

2 participants