feat(build.yml): uncomment screenshot generation step in GitHub Actio…

…ns workflow

The screenshot generation step in the GitHub Actions workflow has been uncommented to ensure that missing screenshots are generated as part of the CI process. This change allows for automated creation and updating of screenshots, which is essential for documentation or UI testing purposes. The use of AWS credentials indicates that the screenshots are likely being stored on AWS S3, and the `sqlite-utils vacuum` command suggests that the database is being cleaned up post-screenshot generation.

.github/workflows/build.yml

@@ -53,14 +53,14 @@ jobs:
       run: |-
         cd main
         datasette . --get / | grep "Abdullah Abid: TIL"
-    # - name: Generate missing screenshots
-    #   env:
-    #     AWS_ACCESS_KEY_ID: ${{ secrets.AWS_ACCESS_KEY_ID }}
-    #     AWS_SECRET_ACCESS_KEY: ${{ secrets.AWS_SECRET_ACCESS_KEY }}
-    #   run: |-
-    #     cd main
-    #     python generate_screenshots.py
-    #     sqlite-utils vacuum tils.db
+    - name: Generate missing screenshots
+      env:
+        AWS_ACCESS_KEY_ID: ${{ secrets.AWS_ACCESS_KEY_ID }}
+        AWS_SECRET_ACCESS_KEY: ${{ secrets.AWS_SECRET_ACCESS_KEY }}
+      run: |-
+        cd main
+        python generate_screenshots.py
+        sqlite-utils vacuum tils.db
     - name: Calculate embeddings and document similarity
       env:
         OPENAI_API_KEY: ${{ secrets.OPENAI_API_KEY }}