wip

Author: landsman

.bruno/bruno.json

@@ -6,4 +6,4 @@
     "node_modules",
     ".git"
   ]
-}
+}

.docs/_cron.md

@@ -1,16 +1,16 @@
 # CRON jobs
 
-You have to allow two extensions: `pg_cron`, `pg_net` for a database to make this
-work.
-See [Supabase Documentation](https://supabase.com/docs/guides/cron).
+You have to allow two extensions: `pg_cron`, `pg_net` for a database to make
+this work. See [Supabase Documentation](https://supabase.com/docs/guides/cron).
 
 You have to run the following commands in SQL Editor of your Supabase project.
 
 ## Generate cron tab
 
 1. Fill out root `.env` file with variables
 2. run tests: `deno run tests`
-3. cron install queries will be generated into the file `cron_jobs.sql` in the root
+3. cron install queries will be generated into the file `cron_jobs.sql` in the
+   root
 4. visit supabase dashboard and run these queries in SQL editor
 
 ## GUI
@@ -21,7 +21,7 @@ There is actually a UI where you can manage your jobs very easily.
 https://supabase.com/dashboard/project/***/integrations/cron/jobs
 ```
 
-*Replace your project ID in the URL*.
+_Replace your project ID in the URL_.
 
 ## Remove existing job
 

.docs/_edge_functions.md

@@ -1,12 +1,15 @@
 # Edge Functions
 
-Basically the same as AWS Lambda, but much better integrated in the whole system. Check [Supabase Documentation](https://supabase.com/docs/guides/functions).
+Basically the same as AWS Lambda, but much better integrated in the whole
+system. Check
+[Supabase Documentation](https://supabase.com/docs/guides/functions).
 
 Code is located in: `./supabase/functions/*`.
 
-Each function can run a very short time (up to 2s) then it's terminated. So it's good to write small scripts with pagination. Database can give you great tooling for that.
-
-Unexpected errors are handled by Sentry. That works good. What should be tweaked is notification about terminated function. It can be done probably by event pushing to Sentry as well.
-
-
+Each function can run a very short time (up to 2s) then it's terminated. So it's
+good to write small scripts with pagination. Database can give you great tooling
+for that.
 
+Unexpected errors are handled by Sentry. That works good. What should be tweaked
+is notification about terminated function. It can be done probably by event
+pushing to Sentry as well.

.docs/_localhost.md

@@ -28,4 +28,4 @@ supabase functions deploy --project-ref xxx
 
 ## Dependencies
 
-run `deno outdated`
+run `deno outdated`

.docs/_podman.md

@@ -1,7 +1,7 @@
 # Podman
 
-If you are switching between Docker Desktop and Podman, you probably got some errors.
-Here is my troubleshooting:
+If you are switching between Docker Desktop and Podman, you probably got some
+errors. Here is my troubleshooting:
 
 ```bash
 docker context ls

.github/action/deno-outdated/action.yml

@@ -1,17 +1,17 @@
 name: Deno Outdated Check
-description: 'Check for outdated Deno dependencies and display them in PR comments'
+description: "Check for outdated Deno dependencies and display them in PR comments"
 
 inputs:
   directory:
-    description: 'Directory where to run the deno outdated check'
+    description: "Directory where to run the deno outdated check"
     required: true
   title:
-      description: 'Message title'
-      required: true
+    description: "Message title"
+    required: true
 
 outputs:
   result:
-    description: 'Result of the outdated check'
+    description: "Result of the outdated check"
     value: ${{ steps.outdated.outputs.result }}
 
 runs:
@@ -29,7 +29,7 @@ runs:
         cat deno.json
         bash ${{ github.workspace }}/.github/action/deno-outdated/deno-outdated.sh
 
-    - name: 'Outdated packages - post'
+    - name: "Outdated packages - post"
       uses: marocchino/sticky-pull-request-comment@v2
       with:
         recreate: true

.github/dependabot.yml

@@ -1,12 +1,12 @@
 version: 2
 updates:
-  - package-ecosystem: 'github-actions'
-    directory: '/'
+  - package-ecosystem: "github-actions"
+    directory: "/"
     schedule:
-      interval: 'monthly'
+      interval: "monthly"
     labels:
-      - 'dependencies'
-      - 'github-actions'
+      - "dependencies"
+      - "github-actions"
     commit-message:
-      prefix: 'ci'
-      include: 'scope'
+      prefix: "ci"
+      include: "scope"

.github/workflows/deploy-supabase.yml

@@ -21,7 +21,7 @@ jobs:
         with:
           version: 2.13.3
 
-      - name: 'Supabase - Remote Connect'
+      - name: "Supabase - Remote Connect"
         env:
           PROJECT_ID: ${{ secrets.SUPABASE_PROJECT_ID }}
           SUPABASE_ACCESS_TOKEN: ${{ secrets.SUPABASE_ACCESS_TOKEN }}

.github/workflows/deploy-web.yml

@@ -36,7 +36,7 @@ jobs:
           cd src/web
           deno run compile
           deno task build
-      
+
       - name: Upload artifact
         uses: actions/upload-pages-artifact@v3
         with:

.github/workflows/pr-supabase.yml

@@ -23,7 +23,7 @@ env:
 
 jobs:
   qa:
-    name: 'QA'
+    name: "QA"
     environment: test
     runs-on: ubuntu-latest
     steps:
@@ -38,16 +38,16 @@ jobs:
       - run: deno lint supabase/*
       - run: deno task tests --reload
 
-      - name: 'Generate cron jobs'
+      - name: "Generate cron jobs"
         uses: actions/upload-artifact@v4
         with:
           name: cron_jobs.sql
           path: cron_jobs.sql
           retention-days: 1
 
-      - name: 'Check Outdated Packages'
+      - name: "Check Outdated Packages"
         uses: ./.github/action/deno-outdated
         id: outdated_supabase
         with:
           directory: ./supabase/functions
-          title: 'Deno Outdated - Supabase'
+          title: "Deno Outdated - Supabase"