[CI] GH Actions workflow_run flows reduce gh context utilization

[adrianriobo]

Component

Quality Engineering

Is your enhancement related to a problem? Please describe

When we use the workflow_run strategy we are passing the full gh context from the PR execution to the workfow_run mostly to being able to update the state on the PR, but all the fields wee need for it can be extracted from the worflow_run payload itself:

Describe the solution you'd like

Check this sample:

https://github.com/containers/podman-desktop-extension-ai-lab/blob/1d91cae0f529681a6cf241ec92bbad102ca8623a/.github/workflows/recipe-catalog-change-trigger.yaml#L10

We can apply same strategy to reduce the information moved between executions

Describe alternatives you've considered

No response

Additional context

No response

[rohanKanojia]

In GitHub workflows, I see these fields used from gh_context.json:

• .event.after
• .event.pull_request.head.sha

crc/.github/workflows/linux-qe-template.yml

Line 46 in 0480a03

commit_sha=$(cat gh_context.json | jq -r '.event.after')

crc/.github/workflows/linux-qe-template.yml

Line 49 in 0480a03

commit_sha=$(cat gh_context.json | jq -r '.event.pull_request.head.sha')

crc/.github/workflows/windows-qe-tpl.yml

Line 66 in 0480a03

commit_sha=$(cat gh_context.json | jq -r '.event.after')

crc/.github/workflows/windows-qe-tpl.yml

Line 69 in 0480a03

commit_sha=$(cat gh_context.json | jq -r '.event.pull_request.head.sha')

all the fields wee need for it can be extracted from the worflow_run payload itself

Shall we remove uploading the github artifact and replace abovementioned occurrences with these (as per github workflow_run docs)?

• github.event.workflow_run.head_sha
• github.event.after (not sure about this)

[adrianriobo]

Yeah I think so, as it seems those values are enough for us and are already accessible