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 usematch_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.
${{ vars.MY_VAR }} expression can produce up to two GH_UsesVariable edges.
Context property
The edge carries acontext property indicating where the reference was found:
with— inside awith:input block of auses:action stepenv— inside the step’senv:blockrun— inline within arun:shell script