From e32acb9796338a51af3fd830cac067456971b5af Mon Sep 17 00:00:00 2001 From: Minionguyjpro Date: Sun, 31 Dec 2023 20:03:50 +0100 Subject: [PATCH] Update README.md --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 6fbb2ae..6eb8cb1 100644 --- a/README.md +++ b/README.md @@ -21,7 +21,7 @@ jobs: The action will tell you it saved the file somewhere around in ``D:\YOURREPONAME\YOURREPONAME\`` and maybe in another directory (depends on how you've defined the output directory in your .iss script). In this case, ``D:\YOURREPONAME\YOURREPONAME\`` is the root directory of your cloned GitHub repository workspace in the action. Keep this path layout in mind if you need it for other things in your workflow. If you'd choose to save the setup file in the root directory (by example not specifing a custom directory) and calling it setup.exe, it would be at ``D:\YOURREPONAME\YOURREPONAME\setup.exe``. --- -| **Key Name** | **Required** | **Example** | **Default Value** | **Description** | -|--------------|--------------|--------------------|-------------------|-----------------------------------------------------------------------------------------------------------------| +| **Key Name** | **Required** | **Example** | **Default Value** | **Description** + | ``path`` | Yes | ``src/setup.iss`` | N/A | Path to input .iss script file. | | ``options`` | No | ``/O+`` | N/A | Extra arguments/options to include. Include the slashes for them. See [this page](https://jrsoftware.org/ishelp/index.php?topic=compilercmdline) for more information. |