PHOENIXCONTACT / PHOENIXCONTACT/tools
Env variables for reusable actions not usable
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 3
- Forks
- 5
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 8
Description
Issue with using environment variables for inputs of reusable actions. Used workaround: https://github.com/orgs/community/discussions/51280
You can see in the draft build-and-test-tool.yml that env variables are set but only being used in steps directly defined in the same yml. Now the variables are set as outputs of the first step as a workaround.
Better than defining every input hardcoded for every step as done previously.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with .github/workflows/build-and-test-tool.yml and compare the environment variables set there with the outputs from the first step and their use in directly defined steps. Reproduce the reusable-action input behavior described in the issue and confirm whether the workflow can use the variables without hardcoding each input.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd, devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100