I created a simple repro :

• main workflow with correct git ref : fix default branch · rducom/repro_bug_Workflow_run@135a6b8 · GitHub
• dependent workflow with incorrect git ref : fix default branch · rducom/repro_bug_Workflow_run@135a6b8 · GitHub

I think this is just a limitation of how this feature works with respect to the way you’re using it. The second workflow is completely independent of the first and will receive a brand new webhook event to trigger it meaning it will just be triggered using the “default” git ref.

Is there a specific reason you’re wanting keep this in a completely separate file? For this situation I’d probably recommend just using a separate job inside the same workflow file. You can use the needs key to prevent your release job from running until your first job completes, and this should preserve the git ref too as it will still be the same webhook event that triggered the workflow.

The second workflow is completely independent of the first

I disagree, the second workflow depends of the first, that’s the intention of the "workflow_run’ feature: let workflows depends on others. Or I completely miss the point.

In my specific case, I need to know there’s a git tag. (More precisely, I want to know the workflow is running because of a tag.). So the git ref is mandatory.

The specific reason I would like to have two separates workflow is just CI structure : having smaller workflow files, and let run specific workflows (like a “publish/release artifact” run only when needed).
I know I can “just put everything in one workflow”, but it seems really more convenient to have distinct workflow, and just run what’s needed when needed.

Moreover, it would allow us to re-use previous parts of the the build. Ex : if I have 5 workflows, and each one need to build and test the whole repository before doing the “remaining part of the job”, it looks like a major resource waste as I could have just build and test the commit once, and then run the “other things” in the 4 or 5 dependent workflows…

That’s why I’m convinced git ref should be propagated from “main” workflows to “dependent workflows”.

I disagree, the second workflow depends of the first, that’s the intention of the "workflow_run’ feature: let workflows depends on others. Or I completely miss the point.

What I meant by this was that as this was an entirely separate workflow it would be treated as such. The variables set in this run would be set at start time and not be inherited from the original.

But it did slip my mind that you’d be able to check inside the triggering webhook event, so I’m glad you managed to find the answer!