Not able to use environment secrets in reusable workflows
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 6.3k
- Forks
- 1.4k
- Avg merge
- 1d 16h
- Merged PRs (30d)
- 24
Description
Describe the bug
Called workflow can not use it's environment secrets. Using organization secrets is not a feasible solution in some cases.
I know that it is in the GitHub public roadmap : https://github.com/orgs/github/projects/4247/views/2?pane=issue&itemId=21176006 , but there does not seem to be any traction on it.
To Reproduce
- Have environment secrets in a repo , with a workflow using them.
- Call this workflow from a caller workflow , existing in different repo.
- You can not use these secrets neither with explicitly mentioning them nor with inherit.
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 the environment-secrets and reusable-workflow reproduction described in the issue, then review the linked GitHub public roadmap item. Done would mean a called workflow in another repository can use the repository's environment secrets through explicit declaration or inherit.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, github-actions
- Domain
- ci-cd
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100