revert auto-formatting

shanegenschaw · Aug 7, 2023 · ae76333 · ae76333
1 parent 2171a58
commit ae76333
Show file tree

Hide file tree

Showing 2 changed files with 15 additions and 14 deletions.
diff --git a/Readme.md b/Readme.md
@@ -14,7 +14,6 @@ See the upstream pull request [`chore: GitHub upgrades` #46](https://github.com/
 ## Example usage in a workflow
 
 Your workflow needs to listen to the following events:
-
 ```
 on:
   pull_request:
@@ -65,16 +64,18 @@ And if you specify a reaction, you have to provide the `GITHUB_TOKEN` env vbl.
 
 ## Inputs
 
-| Input           | Required?            | Description                                                                                                                                    |
-| --------------- | -------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------- |
-| trigger         | Yes                  | The string to look for in pull-request descriptions and comments. The trigger should be placed at the beginning. For example "#build/android". |
-| reaction        | No (default '')      | If set, the specified emoji "reaction" is put on the comment to indicate that the trigger was detected. For example, "rocket".                 |
-| allow_arguments | No (default 'false') | If 'true', script looks for `**` markers that are considered as comment arguments.                                                             |
+| Input | Required? | Description |
+| ----- | --------- | ----------- |
+| trigger | Yes | The string to look for in pull-request descriptions and comments. For example "#build/android". |
+| prefix_only | No (default 'false') | If 'true', the trigger must match the start of the comment. |
+| reaction | No (default '') | If set, the specified emoji "reaction" is put on the comment to indicate that the trigger was detected. For example, "rocket". |
+| allow_arguments | No (default 'false') | If 'true', script looks for `**` markers that are considered as comment arguments. |
+
 
 ## Outputs
 
-| Output       | Description                                                     |
-| ------------ | --------------------------------------------------------------- |
-| triggered    | 'true' or 'false' depending on if the trigger phrase was found. |
-| comment_body | The comment body.                                               |
-| arguments    | The comment arguments.                                          |
+| Output | Description |
+| ------ | ----------- |
+| triggered | 'true' or 'false' depending on if the trigger phrase was found. |
+| comment_body | The comment body. |
+| arguments | The comment arguments. |
diff --git a/action.yml b/action.yml
@@ -1,4 +1,4 @@
-name: "Pull Request Comment Trigger fork"
+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: "node16"
-  main: "dist/index.js"
+  using: 'node16'
+  main: 'dist/index.js'
 branding:
   icon: check-circle
   color: red