chore: update readme

Author: ajaxbits

README.md

@@ -7,12 +7,25 @@ This is meant to faciliate downstream actions or workflows such as matrix builds
 
 This action aims to help you eliminate (or at least reduce) the amount of customization needed in your GHA workflows by pushing your project-specific stuff into `pyproject.toml`.
 
-
 ## Inputs
-- **root-dir**: Directory root for where to begin recursively searching for projects.
-Python projects contained in this directory or lower will be discovered.  Defaults to your repository's root directory.
 
-- **additional-export-paths**: Additional TOML keys to export as part of the projects object. Specify them as json path strings, separated by commas. For example, "tool.foo.bar,baz.qux".
+> `List` type is a newline-delimited string
+> ```yaml
+> exclude-commands: |
+>   project=my-package-1,command=test
+>   project=my-package-2,command=lint
+> ```
+
+> `CSV` type is a comma-delimited string
+> ```yaml
+> additional-export-paths: tool.foo.bar,baz.qux
+> ```
+
+| Input                     | Type        | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+|---------------------------|-------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| `root-dir`                | string      | Directory root for where to begin recursively searching for projects. Python projects contained in this directory or lower will be discovered. Defaults to your repository's root directory.                                                                                                                                                                                                                                                                                                                                                         |
+| `additional-export-paths` | CSV         | Additional TOML keys to export as part of the projects object. Specify them as JSON path strings, separated by commas. For example, `"tool.foo.bar,baz.qux"`.                                                                                                                                                                                                                                                                                                                                                                                        |
+| `exclude-commands`        | string/List | Commands to exclude from processing during project discovery. Any plain string will be parsed as a command. For instance, passing "test" will cause the action to not export any information about "test" commands found in the repo. For project-specific overrides, pass a string of form `project=<name>,command=<name>`. For instance, a value of `project=one,command=lint` would cause the `lint` command to be excluded for a project named `one`, if such a project is discovered. Global and project-specific excludes can be freely mixed. |
 
 ## Outputs
 - **paths**: JSON array of found project path strings
@@ -23,7 +36,6 @@ Python projects contained in this directory or lower will be discovered.  Defaul
 (eg `install`, `test`, `package`, etc.) in all projects, with an array value containing each
 [project object](#project-object-output-shape) that implements the command.
 
-
 ## Project object output shape
 These are the fields for `project` objects in the output:
 
@@ -42,7 +54,6 @@ This is dynamically constructed from the `pyproject.toml` content.
 
 - **exports**: Object with keys specified by the `additional-export-paths` input, and the structured TOML data (parsed as JSON) as the values.
 
-
 ## Project Commands
 In the absence of Python standards for expressing internal project CI/CD/Dev operations, this action tries to unify the various known ways in the wild.
 
@@ -71,7 +82,6 @@ can leverage a task runner tool like [Poe](https://github.com/nat-n/poethepoet)
 
 *If Poetry ever adds support for internal project (CI/CD/Dev) commands separate from published commands, then it will be added to this action.*
 
-
 ### Relevant References / Discussions
 https://discuss.python.org/t/a-new-pep-to-specify-dev-scripts-and-or-dev-scripts-providers-in-pyproject-toml/11457