From b97d36d3023831868b1274262fbc26da96e0546f Mon Sep 17 00:00:00 2001
From: Tony Chen <26252739+TooonyChen@users.noreply.github.com>
Date: Tue, 8 Oct 2024 15:50:48 +1300
Subject: [PATCH] Create main.yml

---
 .github/workflows/main.yml | 28 ++++++++++++++++++++++++++++
 1 file changed, 28 insertions(+)
 create mode 100644 .github/workflows/main.yml

diff --git a/.github/workflows/main.yml b/.github/workflows/main.yml
new file mode 100644
index 0000000..97d0492
--- /dev/null
+++ b/.github/workflows/main.yml
@@ -0,0 +1,28 @@
+            - name: Deploy to Cloudflare Workers with Wrangler
+  # You may pin to the exact commit or the version.
+  # uses: cloudflare/wrangler-action@c25aadc9657b0cdc4786c04e59a6fe92765a783b
+  uses: cloudflare/wrangler-action@v3.1.0
+  with:
+    # Your Cloudflare API Token
+    apiToken: # optional
+    # Your Cloudflare Account ID
+    accountId: # optional
+    # Supresses output from Wrangler commands, defaults to `false`
+    quiet: # optional, default is false
+    # The environment you'd like to deploy your Workers project to - must be defined in wrangler.toml
+    environment: # optional
+    # The relative path which Wrangler commands should be run from
+    workingDirectory: # optional
+    # The version of Wrangler you'd like to use to deploy your Workers project
+    wranglerVersion: # optional
+    # A string of environment variable names, separated by newlines. These will be bound to your Worker as Secrets and must match the names of environment variables declared in `env` of this workflow.
+    secrets: # optional
+    # Commands to execute before deploying the Workers project
+    preCommands: # optional
+    # Commands to execute after deploying the Workers project
+    postCommands: # optional
+    # The Wrangler command (along with any arguments) you wish to run. Multiple Wrangler commands can be run by separating each command with a newline. Defaults to `"deploy"`.
+    command: # optional
+    # A string of environment variable names, separated by newlines. These will be bound to your Worker using the values of matching environment variables declared in `env` of this workflow.
+    vars: # optional
+