Update README

Update README

diff --git a/README.md b/README.md
index 03f68e6..acf3b59 100644
--- a/README.md
+++ b/README.md
@@ -1,39 +1,48 @@
 # GitHub Action - Publish Gem to Rubygems
 
-This is a GitHub Action written to streamline the Ruby gem publication process.  The action sets the Gem Credentials from `GITHUB_TOKEN` and `RUBYGEMS_API_KEY`secrets, and then runs `rake release` in your project root.  You can override this command by setting `RELEASE_COMMAND` environment variable to the script that creates and publishes (this is usually only the case when a repository hosts multiple gems together).
+This is a GitHub Action written to streamline the Ruby gem publication process. The action sets the Gem Credentials from `GITHUB_TOKEN` and `RUBYGEMS_API_KEY`secrets, and then runs `rake release` in your project root. You can override this command by setting `RELEASE_COMMAND` environment variable to the script that creates and publishes (this is usually only the case when a repository hosts multiple gems together).
 
 # Secrets Needed
 
-`GITHUB_TOKEN` - Bundler needs this to create tags on your repo for the release
-`RUBYGEMS_API_KEY` - The Rubygems API Key for an Owner of the Gem you wish to publish.  You can find your API Key by looking in `~/.gem/credentials` or using the [Rubygems API](https://guides.rubygems.org/rubygems-org-api/#misc-methods)
+`GITHUB_TOKEN` - Bundler needs this to create tags on your repo for the release.
+`RUBYGEMS_API_KEY` - The Rubygems API Key for an Owner of the Gem you wish to publish. You can find your API Key by looking in `~/.gem/credentials` or using the [Rubygems API](https://guides.rubygems.org/rubygems-org-api/#misc-methods).
 
 # Environment Variables
 
-`RELEASE_COMMAND` - By default, this will invoke `rake release` to build and publish the gem to Rubygems.  Set this environment variable if you have a custom release command to be invoked
+`RELEASE_COMMAND` - By default, this will invoke `rake release` to build and publish the gem to Rubygems. Set this environment variable if you have a custom release command to be invoked.
+
+`GIT_EMAIL`/`GIT_NAME` - A git identity you wish the tags to by published by.
 
 # Example
 
 `‍``yml
-name: Publish Gem
+name: CI
 
 on:
   push:
     branches:
-      - "*"
-    tags:
-      - v*
+      - main
+
 jobs:
   build:
     runs-on: ubuntu-latest
 
+    steps: (your tests go here)
+
+  publish:
+    if: github.event_name == 'push' && github.ref == 'refs/heads/main'
+    needs: build
+    runs-on: ubuntu-latest
+
     steps:
-      - uses: actions/checkout@v1
+      - uses: actions/checkout@v2
 
       - name: Release Gem
-        if: contains(github.ref, 'refs/tags/v')
-        uses: cadwallion/publish-rubygems-action@master
+        uses: discourse/publish-rubygems-action@v2-beta
         env:
-          GITHUB_TOKEN: ${{secrets.GITHUB_TOKEN}}
-          RUBYGEMS_API_KEY: ${{secrets.RUBYGEMS_API_KEY}}
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+          RUBYGEMS_API_KEY: ${{ secrets.RUBYGEMS_API_KEY }}
           RELEASE_COMMAND: rake release
+          GIT_EMAIL: ci@example.com
+          GIT_NAME: Your CI
 `‍``

GitHub sha: ab3902e43b4be088d85691f35f1f4046034c7928

This commit appears in #2 which was approved by davidtaylorhq. It was merged by CvX.