From 366b6f9db630be3d2d6f53ab4e2072ee4e0bf686 Mon Sep 17 00:00:00 2001
From: Jason Etcovitch <jasonetco@github.com>
Date: Mon, 1 Mar 2021 15:37:08 -0500
Subject: [PATCH] Remove from README

---
 README.md | 17 ++---------------
 1 file changed, 2 insertions(+), 15 deletions(-)

diff --git a/README.md b/README.md
index 8caed0b..a2ce9cc 100644
--- a/README.md
+++ b/README.md
@@ -7,7 +7,6 @@
 
 A GitHub Action for publishing JavaScript Actions! It's designed to act on new releases, and updates the tag with a compiled JS file, using [`@vercel/ncc`](https://github.com/vercel/ncc). The process looks like this:
 
-- Runs the `setup` input (default: `npm ci && npm run build`)
 - Reads the `main` property in your `package.json`
 - Force pushes `action.yml` and the above file to the release's tag
 - Force pushes to the major version tag (ex: `v1.0.0` -> `v1`)
@@ -33,6 +32,8 @@ jobs:
         uses: actions/checkout@v2
         with:
           ref: ${{ github.event.release.tag_name }}
+      - name: Install deps and build
+        run: npm ci && npm run build
       - uses: JasonEtco/build-and-tag-action@v1
         env:
           GITHUB_TOKEN: ${{ github.token }}
@@ -58,20 +59,6 @@ Your `package.json` will probably contain a `dependencies` section, in addition
 
 ## Options
 
-**setup**
-
-You can customize the `setup` script that's run before pushing the files to the tag.
-
-```yaml
-- uses: JasonEtco/build-and-tag-action@v1
-  with:
-    setup: 'npm ci && npm run super-build'
-  env:
-    GITHUB_TOKEN: ${{ github.token }}
-```
-
-The default is `npm ci && npm run build --if-present`. You can disable it entirely by setting `setup: ''`!
-
 **tag_name**
 
 The tag to update. If the workflow event is `release`, it will use the `tag_name` from the event payload. This option can be useful when using this action in a workflow with other actions that generate a release: