feat: delete unmatched docs

aurelio-labs · Sep 1, 2024 · d4d3590 · d4d3590
1 parent 722086e
commit d4d3590
Show file tree

Hide file tree

Showing 4 changed files with 13 additions and 20 deletions.
diff --git a/.github/workflows/docs.yml b/.github/workflows/docs.yml
@@ -48,9 +48,12 @@ jobs:
         with:
           credentials_json: ${{ secrets.GOOGLE_CREDENTIALS }}
       - name: Upload Docs
-        id: upload-directory
-        uses: google-github-actions/upload-cloud-storage@v2
-        with:
-          path: docs/build/html
-          destination: docs-bucket-production/semantic-router
-          parent: false
+        run: |
+          gcloud storage rsync docs/build/html gs://docs-bucket-production/semantic-router --recursive --delete-unmatched-destination
+      # - name: Upload Docs
+      #   id: upload-directory
+      #   uses: google-github-actions/upload-cloud-storage@v2
+      #   with:
+      #     path: docs/build/html
+      #     destination: docs-bucket-production/semantic-router
+      #     parent: false
diff --git a/docs/source/route_layer/local-execution.rst b/docs/source/route_layer/local-execution.rst
@@ -235,7 +235,7 @@ calling
 
 
 Encoders
-========
+--------
 
 You can use alternative Encoders, however, in this example we want to
 showcase a fully-local Semantic Router execution, so we are going to use

diff --git a/docs/source/route_layer/route-filter.rst b/docs/source/route_layer/route-filter.rst
@@ -153,9 +153,9 @@ unrelated to our existing ``Route`` objects?
 In this case, we return ``None`` because no matches were identified.
 
 Demonstrating the Filter Feature
-================================
+--------------------------------
 
-Now, le'’s demonstrate the filter feature. We can specify a subset of
+Now, let's demonstrate the filter feature. We can specify a subset of
 routes to consider when making a classification. This can be useful if
 we want to restrict the scope of possible routes based on some context.
 

diff --git a/docs/source/route_layer/threshold-optimization.rst b/docs/source/route_layer/threshold-optimization.rst
@@ -178,11 +178,6 @@ target route labels:
     Accuracy: 100.00%
 
 
-.. parsed-literal::
-
-    
-
-
 On this small subset we get perfect accuracy — but what if we try we a
 larger, more robust dataset?
 
@@ -285,12 +280,7 @@ can expect the routes to perform on your actual use-case.*
     Accuracy: 34.85%
 
 
-.. parsed-literal::
-
-    
-
-
-Ouch, that’s not so good! Fortunately, we can easily improve our
+Ouch, that's not so good! Fortunately, we can easily improve our
 performance here.
 
 Route Layer Optimization