NO uses GH Action for DD deployment

cdoremus · Mar 22, 2024 · 947f052 · 947f052
1 parent 4915d9e
commit 947f052
Show file tree

Hide file tree

Showing 2 changed files with 4 additions and 2 deletions.
diff --git a/.github/workflows/deploy.yml b/.github/workflows/deploy.yml
@@ -29,5 +29,5 @@ jobs:
       - name: Upload to Deno Deploy
         uses: denoland/deployctl@v1
         with:
-          project: "fresh-webcomponents" # 📝 Update the deploy project name if necessary
+          project: "fresh-webcomponents"
           entrypoint: "./main.ts" # 📝 Update the entrypoint if necessary
diff --git a/README.md b/README.md
@@ -13,6 +13,8 @@ Start the project:
 deno task dev
 ```
 
-The `dev` task runs a build that uses `esbuild` to convert the TypeScript files to JavaScript and bundles all files in `components/wc` into a `wc.esm.js` file in the `static/wc` folder and then starts the Fresh server.
+The `dev` task runs a build that uses `esbuild` to convert the TypeScript files to JavaScript and bundles all files in the `components/wc` folder into the `static/wc/wc.esm.js` file and then starts the Fresh server.
 
 When you update files in `components/wc`, you need to stop the server and run ```deno task dev``` again to rebuild the web component files.
+
+Deployment to Deno Deploy is done via the `deploy.yml` file in `.github/workflows`.