Update README.md

Author: mkcode

README.md

@@ -8,35 +8,21 @@ This Action:
 - Lets you define custom deployment messages (and an optional tag string) using templates.
 - Exposes the Worker Version ID and deployment URL as outputs for downstream steps.
 - Is designed for workflows where you build in GitHub Actions and want clean, traceable deploys in Cloudflare.
-  
-## When to use this instead of the official Cloudflare Action
 
-Use this Action when:
-
-- You want full control over how and where your Worker is built:
-  - You build in GitHub Actions (pnpm, npm, turbo, etc.) and only need Wrangler for the final upload/deploy.
-- You want rich, commit-aware metadata in Cloudflare:
-  - You care about seeing branch, commit, actor, and custom messages in the Cloudflare Versions UI.
-  - You want stable `version_id` outputs to link deploys back to code, PRs, or changelogs.
-- You’re in a monorepo:
-  - You only want to build and deploy when a specific app/package directory changes.
-  - You want an Action that targets a specific `config` path and doesn’t assume a single-project repo.
-- You prefer an explicit upload → deploy flow:
-  - You want `wrangler versions upload` + `wrangler versions deploy <versionId>` semantics instead of a generic `wrangler deploy`.
-- You want your cloudflare deployment dashboard to look like this:
-<img width="2168" height="886" alt="Zen-2025-11-10 at 21 04 46@2x" src="https://github.com/user-attachments/assets/27c329b9-dc68-438d-ba6e-a264bac14390" />
+## When to use this instead of the official Cloudflare Action
 
+### Use this Action if you need:
 
-The official Cloudflare Actions are great if:
+- Monorepo-friendly behavior. Selective path based deployments.
+- Custom build pipelines. Build on GitHub actions.
+- Strong, composable metadata around each version and deployment:
 
-- You want a quick, simple deploy with minimal control.
-- You’re okay with less flexibility around build steps, metadata, and monorepo layouts.
+<img width="2168" height="886" alt="Zen-2025-11-10 at 21 04 46@2x" src="https://github.com/user-attachments/assets/27c329b9-dc68-438d-ba6e-a264bac14390" />
 
-Use this Action if you need:
+### The official Cloudflare Actions are great if:
 
-- Monorepo-friendly behavior.
-- Custom build pipelines.
-- Strong, composable metadata around each deployment.
+- You want a quick, simple deploy with minimal control.
+- You’re okay with less flexibility around build steps and monorepo layouts.
 
 ## Features
 
@@ -265,7 +251,7 @@ jobs:
 
       - name: Upload + deploy via Wrangler Versions with metadata
         id: cf_deploy
-        uses: your-org/wrangler-version-deploy-action-with-metadata@v1
+        uses: mkcode/wrangler-version-deploy-action-with-metadata
         with:
           api_token: ${{ secrets.CLOUDFLARE_API_TOKEN }}
           wrangler_command: "pnpm dlx wrangler@4"
@@ -305,7 +291,7 @@ jobs:
 
       - name: Upload Worker Version with metadata (no deploy)
         id: cf_upload
-        uses: your-org/wrangler-version-deploy-action-with-metadata@v1
+        uses: mkcode/wrangler-version-deploy-action-with-metadata
         with:
           api_token: ${{ secrets.CLOUDFLARE_API_TOKEN }}
           wrangler_command: "pnpm dlx wrangler@4"
@@ -327,7 +313,7 @@ You can combine outputs with other Actions to post deployment info back to PRs:
 ```yaml
 - name: Deploy with metadata
   id: cf_deploy
-  uses: your-org/wrangler-version-deploy-action-with-metadata@v1
+  uses: mkcode/wrangler-version-deploy-action-with-metadata
   with:
     api_token: ${{ secrets.CLOUDFLARE_API_TOKEN }}
     config: "wrangler.toml"
@@ -394,14 +380,14 @@ jobs:
       # - run: pnpm install
       # - run: pnpm build
 
-  name: Upload + deploy worker-app via Versions API with metadata
-  id: cf_deploy
-  uses: your-org/wrangler-version-deploy-action-with-metadata@v1
-  with:
-    api_token: ${{ secrets.CLOUDFLARE_API_TOKEN }}
-    wrangler_command: "pnpm dlx wrangler@4"
-    working_directory: "apps/worker-app"
-    config: "wrangler.toml"
-    upload_args: "--env production"
-    deploy_args: "--env production"
-    message_template: "worker-app: {{repo}}@{{short_sha}} on {{branch}} (run {{run_number}})"
+      - name: Upload + deploy worker-app via Versions API with metadata
+      id: cf_deploy
+      uses: mkcode/wrangler-version-deploy-action-with-metadata
+      with:
+        api_token: ${{ secrets.CLOUDFLARE_API_TOKEN }}
+        wrangler_command: "pnpm dlx wrangler@4"
+        working_directory: "apps/worker-app"
+        config: "wrangler.toml"
+        upload_args: "--env production"
+        deploy_args: "--env production"
+        message_template: "worker-app: {{repo}}@{{short_sha}} on {{branch}} (run {{run_number}})"