Skip to content

Drop confused warning about secret#260

Merged
satterly merged 1 commit intoact10ns:masterfrom
pftg:patch-1
Mar 15, 2023
Merged

Drop confused warning about secret#260
satterly merged 1 commit intoact10ns:masterfrom
pftg:patch-1

Conversation

@pftg
Copy link
Copy Markdown
Contributor

@pftg pftg commented Mar 14, 2023

In GitHub, there are secrets and env entities, and sharing that this action requires a secret is misleading.

In GitHub, there are secrets and env entities, and sharing that this action requires a secret is misleading.
@satterly
Copy link
Copy Markdown
Contributor

Accessing your secrets
To make a secret available to an action, you must set the secret as an input or environment variable in the workflow file. Review the action's README file to learn about which inputs and environment variables the action expects.

https://docs.github.com/en/actions/security-guides/encrypted-secrets

@satterly
Copy link
Copy Markdown
Contributor

👍

@satterly satterly merged commit 3eca730 into act10ns:master Mar 15, 2023
@pftg pftg deleted the patch-1 branch March 15, 2023 08:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants