actions/container-action
1
0
Fork 0
mirror of https://github.com/actions/container-action.git synced 2025-06-15 09:57:41 +00:00
Code Issues Packages Projects Releases Wiki Activity

Correct input name

Browse Source
This commit is contained in:
Nick Alteen 2023-09-01 14:18:59 -04:00
parent 137e75c6a6
commit e3750df619
3 changed files with 8 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
.github/workflows/ci.yml vendored
View File

@ -45,10 +45,10 @@ jobs:
- name: Run the Container - name: Run the Container
id: run id: run
env: env:
INPUT_WHO_TO_GREET: Mona Lisa Octocat INPUT_WHO-TO-GREET: Mona Lisa Octocat
run: | run: |
docker run \ docker run \
--env INPUT_WHO_TO_GREET="Mona Lisa Octocat" \ --env INPUT_WHO-TO-GREET="Mona Lisa Octocat" \
--rm ${{ env.TEST_TAG }} --rm ${{ env.TEST_TAG }}
test-action: test-action:

10
README.md
View File

@ -54,7 +54,7 @@ need to perform some initial setup steps before you can develop your action.
You can pass individual environment variables using the `--env` or `-e` flag. You can pass individual environment variables using the `--env` or `-e` flag.
```bash ```bash
$ docker run --env INPUT_WHO_TO_GREET="Mona Lisa Octocat" actions/container-action $ docker run --env INPUT_WHO-TO-GREET="Mona Lisa Octocat" actions/container-action
::notice file=entrypoint.sh,line=7::Hello, Mona Lisa Octocat! ::notice file=entrypoint.sh,line=7::Hello, Mona Lisa Octocat!
``` ```
@ -63,7 +63,7 @@ need to perform some initial setup steps before you can develop your action.
```bash ```bash
$ cat ./.env.test $ cat ./.env.test
INPUT_WHO_TO_GREET="Mona Lisa Octocat" INPUT_WHO-TO-GREET="Mona Lisa Octocat"
$ docker run --env-file ./.env.test actions/container-action $ docker run --env-file ./.env.test actions/container-action
@ -90,10 +90,10 @@ container actions:
- Inputs are accessed using environment variables with the format - Inputs are accessed using environment variables with the format
`INPUT_<INPUT_NAME>`. For example, this action has an input called `INPUT_<INPUT_NAME>`. For example, this action has an input called
`who-to-greet`, which can be accessed in the entrypoint script using `who-to-greet`, which can be accessed in the entrypoint script using
`INPUT_WHO_TO_GREET`. `INPUT_WHO-TO-GREET`.
```bash ```bash
GREETING="Hello, $INPUT_WHO_TO_GREET!" GREETING="Hello, $INPUT_WHO-TO-GREET!"
``` ```
- GitHub Actions supports a number of different workflow commands such as - GitHub Actions supports a number of different workflow commands such as
@ -140,7 +140,7 @@ So, what are you waiting for? Go ahead and start customizing your action!
```bash ```bash
docker build -t actions/container-action . docker build -t actions/container-action .
docker run --env INPUT_WHO_TO_GREET="Mona Lisa Octocat" actions/container-action docker run --env INPUT_WHO-TO-GREET="Mona Lisa Octocat" actions/container-action
``` ```
1. Commit your changes 1. Commit your changes

2
entrypoint.sh
View File

@ -1,7 +1,7 @@
#!/bin/sh -l #!/bin/sh -l
# Use INPUT_<INPUT_NAME> to get the value of an input # Use INPUT_<INPUT_NAME> to get the value of an input
GREETING="Hello, $INPUT_WHO_TO_GREET!" GREETING="Hello, $INPUT_WHO-TO-GREET!"
# Use workflow commands to do things like set debug messages # Use workflow commands to do things like set debug messages
echo "::notice file=entrypoint.sh,line=7::$GREETING" echo "::notice file=entrypoint.sh,line=7::$GREETING"