Hmm I think you are correct,. in this specific example it is looking for a Task already executed on this commit hash:
None
you can check this one, it creates a Task and tests it:
None

Hi @<1628927672681762816:profile|GreasyKitten62>
Notice that in the github actions example this psecific Task is executed on the GitHub backend, the Task it creates is executed on the clearml-agent.
So basically:
Action -> Git worker -> task_stats_to_comment.py -> Task Pushed to Queue -> Clearml-Agent -> Task execution is here

Does that make sense ?

Hi @<1523701205467926528:profile|AgitatedDove14>
Thanks for responding. I see where you are getting to but it doesn't appear there's any task being created here. The task_stats_to_comment.py is being run on the GitHub runner hence it is able to access the Github_event environment variable.
What you mentioned seems like is the case for my particular setup where the step in Github Actions triggers a clearml task by using the clearml-task command and the execution is happening on the clearml-agent.