Skip to content

Commit

Permalink
fix typos in action.yml (#543)
Browse files Browse the repository at this point in the history
Closes #542

Rebases #542 with the generated docs, and opening as myself so that
integration tests pass.

---------

Signed-off-by: Ahmad Nassri <[email protected]>
Co-authored-by: Ahmad Nassri <[email protected]>
  • Loading branch information
sethvargo and ahmadnassri authored Sep 10, 2024
1 parent 6ffa584 commit 1671c7f
Show file tree
Hide file tree
Showing 2 changed files with 6 additions and 6 deletions.
6 changes: 3 additions & 3 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -100,13 +100,13 @@ jobs:
merged). To remove all values, set the value to the literal string `{}`.

If both `env_vars` and `env_vars_file` are specified, the keys in
`env_vars` will take precendence over the keys in `env_vars_files`.
`env_vars` will take precendence over the keys in `env_vars_file`.

- <a name="env_vars_file"></a><a href="#user-content-env_vars_file"><code>env_vars_file</code></a>: _(Optional)_ Path to a file on disk, relative to the workspace, that defines
environment variables. The file can be newline-separated KEY=VALUE pairs,
JSON, or YAML format. If both `env_vars` and `env_vars_file` are
specified, the keys in env_vars will take precendence over the keys in
env_vars_files.
env_vars_file.

NAME=person
[email protected]\,[email protected]
Expand All @@ -115,7 +115,7 @@ jobs:
described in `env_vars`. You do not have to escape YAML or JSON.

If both `env_vars` and `env_vars_file` are specified, the keys in
`env_vars` will take precendence over the keys in `env_vars_files`.
`env_vars` will take precendence over the keys in `env_vars_file`.

**⚠️ DEPRECATION NOTICE:** This input is deprecated and will be removed in
the next major version release.
Expand Down
6 changes: 3 additions & 3 deletions action.yml
Original file line number Diff line number Diff line change
Expand Up @@ -83,7 +83,7 @@ inputs:
merged). To remove all values, set the value to the literal string `{}`.
If both `env_vars` and `env_vars_file` are specified, the keys in
`env_vars` will take precendence over the keys in `env_vars_files`.
`env_vars` will take precendence over the keys in `env_vars_file`.
required: false

env_vars_file:
Expand All @@ -92,7 +92,7 @@ inputs:
environment variables. The file can be newline-separated KEY=VALUE pairs,
JSON, or YAML format. If both `env_vars` and `env_vars_file` are
specified, the keys in env_vars will take precendence over the keys in
env_vars_files.
env_vars_file.
NAME=person
[email protected]\,[email protected]
Expand All @@ -101,7 +101,7 @@ inputs:
described in `env_vars`. You do not have to escape YAML or JSON.
If both `env_vars` and `env_vars_file` are specified, the keys in
`env_vars` will take precendence over the keys in `env_vars_files`.
`env_vars` will take precendence over the keys in `env_vars_file`.
**⚠️ DEPRECATION NOTICE:** This input is deprecated and will be removed in
the next major version release.
Expand Down

0 comments on commit 1671c7f

Please sign in to comment.