GH_UsesVariable

[Workflow] Step references a variable by name — GH_WorkflowStep → GH_RepoVariable / GH_OrgVariable (name match)

Edge Schema

• Source: GH_WorkflowStep
• Destination: GH_RepoVariable, GH_OrgVariable
• Traversable: ❌

General Information

The non-traversable GH_UsesVariable edge links a workflow step to the variable it references via a ${{ vars.NAME }} expression. This edge maps variable consumption within workflows. Unlike secrets, variable values are readable via the API, making them lower sensitivity, but they can still influence workflow behavior.

Matching strategy

Edges use match_by: property with two matchers to disambiguate between variables with the same name across repositories:

• GH_RepoVariable is matched by name + repository_id.
• GH_OrgVariable is matched by name + environmentid.

This means one ${{ vars.MY_VAR }} expression can produce up to two GH_UsesVariable edges.

Context property

The edge carries a context property indicating where the reference was found:

• with — inside a with: input block of a uses: action step
• env — inside the step’s env: block
• run — inline within a run: shell script