actions / actions/runner

Post Run action inputs become null

Open
#2,800 5 comments 7 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
C#
Stars
6.3k
Forks
1.4k
Avg merge
1d 16h
Merged PRs (30d)
24

Description

Describe the bug

Post Run action inputs become null.

Happen when workflow file looks like this.

workflow --call--> action --call--> action

To Reproduce
Steps to reproduce the behavior:

  1. fork https://github.com/kevinchen-pimq/action-input-poc
  2. Run POC workflow

Expected behavior

Inputs value should not be null.

Runner Version and Platform

Version of your runner?

2.308.0

OS of the machine running the runner? OSX/Windows/Linux/...

  Ubuntu
  20.04.6
  LTS

What's not working?

Please include error messages and screenshots.
workflow run:
https://github.com/kevinchen-pimq/action-input-poc/actions/runs/5973798158

Case 1:
workflow --call--> action test-post-run-input
Post run is as expected.

Case 2:
workflow --call--> action extra-step --call--> action test-post-run-input
Post run test-post-run-input inputs become null.

image

Job Log Output

If applicable, include the relevant part of the job / step log output here. All sensitive information should already be masked out, but please double-check before pasting here.

https://github.com/kevinchen-pimq/action-input-poc/actions/runs/5973798158

Runner and Worker's Diagnostic Logs

If applicable, add relevant diagnostic log information. Logs are located in the runner's _diag folder. The runner logs are prefixed with Runner_ and the worker logs are prefixed with Worker_. Each job run correlates to a worker log. All sensitive information should already be masked out, but please double-check before pasting here.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Run the linked action-input-poc workflow and compare the single-action case with the nested workflow → extra-step → test-post-run-input case. Review the linked workflow run and the runner's Worker_ and Runner_ diagnostic logs to trace when the post-run inputs become null. Done means the reproduced nested case retains the expected input values.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
ci-cd, tooling
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
28/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.