-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #2 from evo-lua/readme-usage-update
Add some basic usage instructions to the README
- Loading branch information
Showing
2 changed files
with
20 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,2 +1,17 @@ | ||
# evo-setup-action | ||
|
||
GitHub Action to set up the Evo.lua runtime (for CI runs) | ||
|
||
## Usage | ||
|
||
You can find an example here: [test.yml](.github/workflows/test.yml). Here's what you need to know: | ||
|
||
* Set the `version` input to the desired runtime version (must be a [tagged release](https://github.com/evo-lua/evo-runtime/releases)) | ||
* You can use `main` or a [tagged release](https://github.com/evo-lua/evo-setup-action/releases) for this action itself by setting `@<tag>` | ||
* On Linux, the action will take longer to run as it has to install dependencies first | ||
|
||
The above workflow is automatically tested, so you can always use it as a reference. | ||
|
||
## Status | ||
|
||
Very experimental and expected to evolve over time (just like the `evo` runtime itself). |