Composite: Nested actions post steps have the wrong context
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
Post steps in of nested composite actions have the wrong context. It's the context of the parent that is used instead of it's own context.
To Reproduce
- Create a composite action with a post step (like caching) that uses an input
- Create a composite action that calls the action created in 1
- Run the action created in 2 in a worflow
Expected behavior
The nested action post step can use the input of it's context.
Runner Version and Platform
Version of your runner? Latest hosted
OS of the machine running the runner? All
What's not working?
Interpolation doesn't work since the context is wrong
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 by reproducing the nested composite-action workflow described: a composite action with a post step using an input, called by another composite action. Compare the post-step context with the nested action's own input context, and review issue #2009 for related behavior. Done means nested post steps interpolate their own inputs rather than the parent action's context.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, github-actions
- Domain
- ci-cd, devtools
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100