Upgrade action and README.md (w9jds#7)

- A lot has changed since the initial beta of actions, this update will bring it up to par with the current way actions are configured. 
- The example also shows how to pass a build artifact to the deployment job.

Author: w9jds

Dockerfile

@@ -1,16 +1,10 @@
-
 FROM node:10-slim
 
-LABEL version="1.0.0"
+LABEL version="1.1.0"
 LABEL repository="https://github.com/w9jds/firebase-action"
 LABEL homepage="https://github.com/w9jds/firebase-action"
 LABEL maintainer="Jeremy Shore <[email protected]>"
 
-LABEL com.github.actions.name="GitHub Action for Firebase"
-LABEL com.github.actions.description="Wraps the firebase-tools CLI to enable common commands."
-LABEL com.github.actions.icon="package"
-LABEL com.github.actions.color="gray-dark"
-
 RUN npm install -g firebase-tools
 
 COPY LICENSE README.md /

README.md

@@ -2,29 +2,68 @@
 
 This Action for [firebase-tools](https://github.com/firebase/firebase-tools) enables arbitrary actions with the `firebase` command-line client.
 
-### Secrets
+## Inputs
+
+* `args` - **Required**. This is the arguments you want to use for the `firebase` cli
 
-* `FIREBASE_TOKEN` - **Required**. The token to use for authentication. This token can be aquired through the `firebase login:ci` command.
 
-### Environment variables
+## Environment variables
+
+* `FIREBASE_TOKEN` - **Required**. The token to use for authentication. This token can be aquired through the `firebase login:ci` command.
 
 * `PROJECT_ID` - **Optional**. To specify a specific project to use for all commands, not required if you specify a project in your `.firebaserc` file.
 
-#### Example
+## Example
 
 To authenticate with Firebase, and deploy to Firebase Hosting:
 
-```hcl
-action "Deploy Production Site" {
-  uses = "w9jds/firebase-action@master"
-  args = "deploy --only hosting:prod"
-  env = {
-    PROJECT_ID = "new-eden-storage-a5c23"
-  }
-  secrets = ["FIREBASE_TOKEN"]
-}
+```yaml
+name: Build and Deploy
+on:
+  push:
+    branches:
+      - master
+
+jobs:
+  build:
+    name: Build
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout Repo
+        uses: actions/checkout@master
+      - name: Install Dependencies
+        run: npm install
+      - name: Build
+        run: npm run build-prod
+      - name: Archive Production Artifact
+        uses: actions/upload-artifact@master
+        with:
+          name: dist
+          path: dist
+  deploy:
+    name: Deploy
+    needs: build
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout Repo
+        uses: actions/checkout@master
+      - name: Download Artifact
+        uses: actions/download-artifact@master
+        with:
+          name: dist
+      - name: Deploy to Firebase
+        uses: w9jds/firebase-action@develop
+        with:
+          args: deploy --only hosting:prod
+        env:
+          FIREBASE_TOKEN: ${{ secrets.FIREBASE_TOKEN }}
 ```
 
 ## License
 
 The Dockerfile and associated scripts and documentation in this project are released under the [MIT License](LICENSE).
+
+
+### Recommendation
+
+If you decide to do seperate jobs for build and deployment (which is probably advisable), then make sure to clone your repo as the Firebase-cli requires the firebase repo to deploy (specifically the `firebase.json`)

action.yaml

@@ -0,0 +1,9 @@
+name: 'GitHub Action for Firebase'
+author: 'Jeremy Shore'
+description: 'Wraps the firebase-tools CLI to enable common commands.'
+branding:
+  icon: 'package'
+  color: 'gray-dark'
+runs:
+  using: 'docker'
+  image: 'Dockerfile'

entrypoint.sh

@@ -1,4 +1,4 @@
-#!/bin/sh
+#!/bin/sh -l
 
 set -e
 
@@ -8,6 +8,7 @@ if [ -z "$FIREBASE_TOKEN" ]; then
 fi
 
 if [ -n "$PROJECT_ID" ]; then
+    echo "setting firebase project to $PROJECT_ID"
     firebase use --add $PROJECT_ID
 fi