Skip to content

Update README.md #9

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
smac89 wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Update README.md #9

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -31,8 +31,8 @@ Each action will run when it detects an issue with it's name was created. It doe
### Creating environment variables
:speech_balloon: There are two ways to create [environment variables](https://help.github.com/en/actions/automating-your-workflow-with-github-actions/using-environment-variables#about-environment-variables):

- :information_source: By using the env keyword on the _entire workflow_, a _job_ or a _step_. See [`env`](https://help.github.com/en/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#env). ***Note: This variable CAN be used in the same place where it was created***
- :information_source: Through Github Actions [`set-env`](https://help.github.com/en/actions/automating-your-workflow-with-github-actions/development-tools-for-github-actions#set-an-environment-variable-set-env). This will create an environment variable that can be used by all subsequent steps. ***Note: Variables created this way CANNOT be used in the same step where they were created, however following steps can see that variable***
- :information_source: By using the env keyword on the _entire workflow_, a _job_ or a _step_. See [`env`](https://help.github.com/en/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#env). ***Note: This variable CAN be used in the same step where it was created***
- :information_source: Through Github Actions [`set-env`](https://help.github.com/en/actions/automating-your-workflow-with-github-actions/development-tools-for-github-actions#set-an-environment-variable-set-env). This will create an environment variable that can be used by all subsequent steps. ***Note: Variables created this way CANNOT be used in the same step where they were created, however proceeding steps can see and use that variable***

:fast_forward: **See [`step_param_from_env.yml`](https://github.com/smac89/gh-actions-samples/blob/898cfc848d9a0aa073416ea615ce880ed7488c0e/.github/workflows/step_param_from_env.yml#L17)**

Expand Down