testing `yarn install` from wercker

wercker.yml

@@ -14,9 +14,6 @@ test:
       name: install dependencies
       code: |
         yarn global add npm@4
-        # add assets-webpack-plugin individually
-        # because `yarn install` couldn't find package from the "npm" registry
-        yarn add assets-webpack-plugin
         yarn install
 
     - script:
@@ -41,9 +38,6 @@ build-prod:
       name: install dependencies
       code: |
         yarn global add npm@4
-        # add assets-webpack-plugin individually
-        # because `yarn install` couldn't find package from the "npm" registry
-        yarn add assets-webpack-plugin
         yarn install --production
 
     - script:
@@ -66,9 +60,6 @@ build-dev:
       name: install dependencies
       code: |
         yarn global add npm@4
-        # add assets-webpack-plugin individually
-        # because `yarn install` couldn't find package from the "npm" registry
-        yarn add assets-webpack-plugin
         yarn install
 
     - script:
@@ -104,7 +95,7 @@ prepare-to-release: # would be run on release branch
         git push -u origin HEAD:tmp/release-$RELEASE_VERSION
 
 
-release:
+release-to-github: # would be run on temporary release branch
   steps:
     - script:
       name: get version
@@ -112,9 +103,6 @@ release:
         export RELEASE_VERSION=`npm run version --silent`
         echo "export RELEASE_VERSION=$RELEASE_VERSION"
 
-
-release-to-github: # would be run on temporary release branch
-  steps:
     - github-create-release:
       token: $GITHUB_TOKEN
       tag: v$RELEASE_VERSION
@@ -130,3 +118,11 @@ release-to-github: # would be run on temporary release branch
         git remote add origin $GITHUB_ORIGIN
         # remove branch
         git push --delete origin $WERCKER_GIT_BRANCH
+
+
+# the pipeline that do nothing
+#  this is needed while wercker can't detect specified branch pushed
+empty:
+  steps:
+    - script:
+      code: echo "this is $WERCKER_GIT_BRANCH branch"