chore: upgrade GitHub Actions functionality per deprecations

Author: shanegenschaw

Readme.md

@@ -4,6 +4,13 @@ Look for a "trigger word" in a pull-request description or comment, so that late
 
 <!-- TODO release workflow-preprocessor This is most useful in tandem with [workflow-preprocessor], so that you don't have to be writing a ton of `if`s all down the line. -->
 
+:warning: This is a fork of the [Khan/pull-request-comment-trigger](https://github.com/Khan/pull-request-comment-trigger) action ([marketplace](https://github.com/marketplace/actions/pull-request-comment-trigger)), with upgrades for deprecated GitHub Actions functionality:
+
+- [2022-10-11-github-actions-deprecating-save-state-and-set-output-commands](https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/)
+- [2022-09-22-github-actions-all-actions-will-begin-running-on-node16-instead-of-node12](https://github.blog/changelog/2022-09-22-github-actions-all-actions-will-begin-running-on-node16-instead-of-node12/)
+
+See the upstream pull request [`chore: GitHub upgrades` #46](https://github.com/Khan/pull-request-comment-trigger/pull/46) for more details.
+
 ## Example usage in a workflow
 
 Your workflow needs to listen to the following events:
@@ -22,7 +29,7 @@ jobs:
   deploy:
     runs-on: ubuntu-latest
     steps:
-      - uses: khan/pull-request-comment-trigger@v1.1.0
+      - uses: shanegenschaw/pull-request-comment-trigger@v2.0.0
         id: check
         with:
           trigger: '@deploy'

action.yml

@@ -1,4 +1,4 @@
-name: 'Pull Request Comment Trigger'
+name: 'Pull Request Comment Trigger fork'
 description: 'Look for a "trigger word" in a pull-request description or comment, so that later steps can know whether or not to run.'
 inputs:
   reaction:
@@ -18,8 +18,8 @@ outputs:
   comment_body:
     description: The comment body.
 runs:
-  using: 'node12'
+  using: 'node16'
   main: 'dist/index.js'
 branding:
   icon: check-circle
-  color: red
+  color: red