From 36fc4f9c0a800331ccc6ac37457e00f7f11f8f1e Mon Sep 17 00:00:00 2001 From: ChristopherHX Date: Sun, 23 Jul 2023 17:54:54 +0200 Subject: [PATCH] Fix local composite action context data Action.Id is the correct parent step id, by using ExecutionContext.Id all post steps of remote Actions are executed with the contextdata of the parent composite action --- src/Runner.Worker/ActionRunner.cs | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/Runner.Worker/ActionRunner.cs b/src/Runner.Worker/ActionRunner.cs index a17e332b58c..916817e9e97 100644 --- a/src/Runner.Worker/ActionRunner.cs +++ b/src/Runner.Worker/ActionRunner.cs @@ -89,7 +89,7 @@ Action.Reference is Pipelines.RepositoryPathReference localAction && string.Equals(localAction.RepositoryType, Pipelines.PipelineConstants.SelfAlias, StringComparison.OrdinalIgnoreCase)) { var actionManager = HostContext.GetService(); - var prepareResult = await actionManager.PrepareActionsAsync(ExecutionContext, compositeHandlerData.Steps, ExecutionContext.Id); + var prepareResult = await actionManager.PrepareActionsAsync(ExecutionContext, compositeHandlerData.Steps, Action.Id); // Reload definition since post may exist now (from embedded steps that were JIT downloaded) definition = taskManager.LoadAction(ExecutionContext, Action);