From 00f3c7175c1fce5fcf5fedda15d2e955b49bcfed Mon Sep 17 00:00:00 2001 From: Filament Bot Date: Thu, 26 Feb 2026 18:05:45 +0000 Subject: [PATCH] [automated] Updating /docs due to commit e4fa86f Full commit hash is e4fa86fb01bb3099e30bc0f5016d6211485a8527 DOCS_ALLOW_DIRECT_EDITS --- docs/dup/test_ci_renderdiff.html | 2 +- docs/main/filament.html | 398 +++++++++++++++---------------- docs/searchindex.js | 2 +- docs/searchindex.json | 2 +- 4 files changed, 202 insertions(+), 202 deletions(-) diff --git a/docs/dup/test_ci_renderdiff.html b/docs/dup/test_ci_renderdiff.html index 62c40d7be3..15d4bd9563 100644 --- a/docs/dup/test_ci_renderdiff.html +++ b/docs/dup/test_ci_renderdiff.html @@ -225,7 +225,7 @@ into branch of filament-assets. This branch is pai filament repo.

As an example, imagine I am working on a PR, and I've uploaded my change, which is in a branch called my-pr-branch, to filament. This PR requires updating the golden. We would do -it in the following fashion

+it in the following fashion on a macOS machine:

Using a script to update the golden repo