Skip to content

Commit

Permalink
docs: small fix for better readability
Browse files Browse the repository at this point in the history
  • Loading branch information
gliech committed May 8, 2021
1 parent e5b29d2 commit 356de66
Showing 1 changed file with 5 additions and 5 deletions.
10 changes: 5 additions & 5 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -44,21 +44,21 @@ steps:
## Inputs
#### `name`
**Required** Name of the secret that you want to create/update.
**(Required)** Name of the secret that you want to create/update.

#### `value`
**Required** Value of the secret that you want to create/update.
**(Required)** Value of the secret that you want to create/update.
> This action cannot mask the provided secret value in workflow logs. If you do
> not want the value to appear the outputs of your workflow runs, it has to be
> masked before it is provided to this action as input.
> not want the secret value to appear in the output of your workflow run, you
> have to mask it before you provide it to this action as input.

#### `location`
Name of a GitHub repository or organization where you want to create/update a
secret. Expects the notation `owner/repo` for repositories. Defaults to the
repository that invoked the workflow.

#### `pa_token`
**Required** Personal access token with permission to modify repository or
**(Required)** Personal access token with permission to modify repository or
organization secrets.
> For more information on PATs see the GitHub docs article on [creating a
> personal access token][1]. The GitHub Secrets API requires the `repo` scope to
Expand Down

0 comments on commit 356de66

Please sign in to comment.