Updates instructions in README

Author: kennethormandy

README.md

@@ -24,7 +24,7 @@ You’ll be asked to login again, and afterwards your token will be displayed li
 token: a142e09a6b13a21be512b141241c7123
 ```
 
-![Getting your token from the Surge CLI.](https://surge.sh/images/help/integrating-with-circleci.gif)
+![Getting your token from the Surge CLI.](http://localhost:5001/images/help/integrating-with-circleci.gif)
 
 ### Adding Surge as a `devDependency` to a `package.json` file
 
@@ -44,79 +44,67 @@ Next, run this command to save Surge as a `devDependency`, so CircleCI will inst
 npm install --save-dev surge
 ```
 
-<!--
+#### Double-check your tests
 
-### Add your project’s repository to CircleCI
-
-Now you can login and setup a new project on CircleCI. Add your project’s GitHub repository to your CircleCI projects:
-
-![Add the GitHub repository your project is stored in. This example is using the surge-sh/example-circleci repo.](https://surge.sh/images/help/integrating-with-circleci-2.png)
+If you needed to add a new `package.json` file, you’ll want to make one small change. It’s possible your initial build will fail if you don’t have any tests, or if you have the default test command in your `package.json`.
 
-### Define your Setup and Test Commands
+You can add tests or just clear this out of your `package.json` file entirely, changing:
 
-Now you’re ready to run `surge` on CircleCI. Your CircleCI setup commands run before the deployment command.
-
-![](https://surge.sh/images/help/integrating-with-circleci-3.png)
+```sh
+"scripts": {
+  "test": "echo \"Error: no test specified.\" && exit 1"
+}
+```
 
-Your setup commands should look like this:
+…into:
 
 ```sh
-# Install the latest version of Node.js
-nvm install stable
-nvm use stable
-
-# Install Surge as a devDependency
-npm install
+"scripts": {
+  "test": "echo \"Error: no test specified.\""
+}
 ```
 
-After you push you successfully to your repository, CircleCI will run your Test Pipeline commands, which is when you can publish your project with Surge:
+Commit this change, and push it to your repo. Now, even if you don’t have tests, CircleCI will be able to move onto the deployment command.
 
-```sh
-# Run your tests (if you have any)
-npm test
+### Add your project’s repository to CircleCI
 
-# Run Surge
-surge --project ./ --domain example-circleci.surge.sh
-```
+Now you can login and setup a new project on CircleCI. Choose the GitHub organisation your project is in (_surge-sh_ in this example) and then build your project’s GitHub repository:
 
-### Add Environment Variables
+![Add the GitHub repository your project is stored in. This example is using the surge-sh/example-circleci repo.](http://localhost:5001/images/help/integrating-with-circleci-2.png)
 
-Press _Environment Variables_ next, and you’ll be able to secretly add your email address and token so CircleCI can login to Surge for you:
+### Add Environment Variables
 
-![Environment Variables is listed under your project settings.](https://surge.sh/images/help/integrating-with-circleci-4.png)
+Choose _Environment Variables_ from your project settings, and you’ll be able to secretly add your email address and token so CircleCI can login to Surge for you:
 
 Create one environment variable called:
 
 ```
 SURGE_LOGIN
 ```
 
-…and set it to the email address you use with Surge. Next, add another environment variable called:
+…and set it to the email address you use with Surge.
+
+![Adding SURGE_TOKEN` as an environment variable.](http://localhost:5001/images/help/integrating-with-circleci-3.png)
+
+Next, add another environment variable called:
 
 ```
 SURGE_TOKEN
 ```
 
 …and set it to your Surge token.
 
-![Adding `SURGE_LOGIN` and `SURGE_TOKEN` as environment variables.](https://surge.sh/images/help/integrating-with-circleci-5.png)
+![Adding SURGE_TOKEN` as an environment variable.](http://localhost:5001/images/help/integrating-with-circleci-4.png)
 
-### Add a deployment script
+## Run Surge on CircleCI
 
-Push to your repository, and your Setup and Test commands should run, triggering your tests to run on CircleCI. Now, CircleCI will let you move onto adding a script for Continuous Deployment. You can press the button labeled _Set up Continuous Deployment_ or access this section under your project settings:
+Now you’re ready to run your deployment step with `surge` on CircleCI.
 
-![Adding a custom script for continuous deployment.](https://surge.sh/images/help/integrating-with-circleci-6.png)
 
-Add a _Custom Script_ and enter the command you want to run with Surge, for example:
-
-```sh
-surge --project ./ example-circleci.surge.sh
-```
+***
 
 Now, when you push your project to GitHub again, this command will be run and your project will get published automatically.
 
--->
-
 ## License
 
 [The MIT License (MIT)](LICENSE.md)