fix GH_Uses* edge descriptions

Author: JonasBK

docs/official-docs/opengraph/extensions/github/edges/gh_usessecret.mdx

@@ -1,6 +1,6 @@
 ---
 title: 'GH_UsesSecret'
-description: '[Workflow] Step references a secret by name — GH_WorkflowStep → GH_Secret (name match)'
+description: '[Workflow] Step references a secret by name — GH_WorkflowStep → GH_RepoSecret / GH_OrgSecret (name match)'
 ---
 
 <img noZoom src="/assets/enterprise-AND-community-edition-pill-tag.svg" alt="Applies to BloodHound Enterprise and CE"/>
@@ -18,7 +18,7 @@ The traversable `GH_UsesSecret` edge links a workflow step to the secret it refe
 Edges use `match_by: property` with two matchers to disambiguate between secrets with the same name across repositories:
 
 - **[GH_RepoSecret](/opengraph/extensions/github/nodes/gh_reposecret)** is matched by `name` + `repository_id` (the GitHub node_id of the repository).
-- **GH_OrgSecret** is matched by `name` + `environmentid` (the node_id of the organization, which acts as the org-level secret scope).
+- **[GH_OrgSecret](/opengraph/extensions/github/nodes/gh_orgsecret)** is matched by `name` + `environmentid` (the node_id of the organization, which acts as the org-level secret scope).
 
 This means one `${{ secrets.MY_SECRET }}` expression in a workflow can produce up to two `GH_UsesSecret` edges — one to the repo-level secret and one to the org-level secret — reflecting that either could supply the value at runtime depending on scope precedence.
 

docs/official-docs/opengraph/extensions/github/edges/gh_usesvariable.mdx

@@ -1,6 +1,6 @@
 ---
 title: 'GH_UsesVariable'
-description: '[Workflow] Step references a variable by name — GH_WorkflowStep → GH_Variable (name match)'
+description: '[Workflow] Step references a variable by name — GH_WorkflowStep → GH_RepoVariable / GH_OrgVariable (name match)'
 ---
 
 <img noZoom src="/assets/enterprise-AND-community-edition-pill-tag.svg" alt="Applies to BloodHound Enterprise and CE"/>
@@ -17,8 +17,8 @@ The non-traversable `GH_UsesVariable` edge links a workflow step to the variable
 
 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` (the GitHub node_id of the repository).
-- **GH_OrgVariable** is matched by `name` + `environmentid` (the node_id of the organization, which acts as the org-level variable scope).
+- **[GH_RepoVariable](/opengraph/extensions/github/nodes/gh_repovariable)** is matched by `name` + `repository_id` (the GitHub node_id of the repository).
+- **[GH_OrgVariable](/opengraph/extensions/github/nodes/gh_orgvariable)** is matched by `name` + `environmentid` (the node_id of the organization, which acts as the org-level variable scope).
 
 This means one `${{ vars.MY_VAR }}` expression can produce up to two `GH_UsesVariable` edges — one to the repo-level variable and one to the org-level variable.
 

docs/official-docs/opengraph/extensions/github/schema.mdx

@@ -9,7 +9,7 @@ icon: circle-nodes
 
 **Name:** SOGitHub<br />
 **Display Name:** GitHub Extension (by SpecterOps)<br />
-**Version:** v1.2.1<br />
+**Version:** v1.2.2<br />
 **Namespace:** GH<br />
 **Environment Kind:** GH_Organization<br />
 **Source Kind:** GitHub
@@ -153,8 +153,8 @@ This file is automatically generated from the [extension schema definition file]
 | [GH_ToggleDiscussionAnswer](/opengraph/extensions/github/edges/gh_togglediscussionanswer) | ❌ | [Repository] Repo role can toggle discussion answers |
 | [GH_ToggleDiscussionCommentMinimize](/opengraph/extensions/github/edges/gh_togglediscussioncommentminimize) | ❌ | [Repository] Repo role can minimize discussion comments |
 | [GH_TransferRepository](/opengraph/extensions/github/edges/gh_transferrepository) | ❌ | [Organization] Org role can transfer repositories |
-| [GH_UsesSecret](/opengraph/extensions/github/edges/gh_usessecret) | ❌ | [Workflow] Step references a secret by name — GH_WorkflowStep → GH_Secret (name match) |
-| [GH_UsesVariable](/opengraph/extensions/github/edges/gh_usesvariable) | ❌ | [Workflow] Step references a variable by name — GH_WorkflowStep → GH_Variable (name match) |
+| [GH_UsesSecret](/opengraph/extensions/github/edges/gh_usessecret) | ❌ | [Workflow] Step references a secret by name — GH_WorkflowStep → GH_RepoSecret / GH_OrgSecret (name match) |
+| [GH_UsesVariable](/opengraph/extensions/github/edges/gh_usesvariable) | ❌ | [Workflow] Step references a variable by name — GH_WorkflowStep → GH_RepoVariable / GH_OrgVariable (name match) |
 | [GH_ValidToken](/opengraph/extensions/github/edges/gh_validtoken) | ✅ | Secret scanning alert contains a valid, active token belonging to this user |
 | [GH_ViewDependabotAlerts](/opengraph/extensions/github/edges/gh_viewdependabotalerts) | ❌ | [Repository] Repo role can view Dependabot alerts |
 | [GH_ViewSecretScanningAlerts](/opengraph/extensions/github/edges/gh_viewsecretscanningalerts) | ❌ | [Repository] Role can view secret scanning alerts |

extension/schema.json

@@ -2,7 +2,7 @@
   "schema": {
     "name": "SOGitHub",
     "display_name": "GitHub Extension (by SpecterOps)",
-    "version": "v1.2.1",
+    "version": "v1.2.2",
     "namespace": "GH"
   },
   "node_kinds": [
@@ -778,12 +778,12 @@
     },
     {
       "name": "GH_UsesSecret",
-      "description": "[Workflow] Step references a secret by name — GH_WorkflowStep → GH_Secret (name match)",
+      "description": "[Workflow] Step references a secret by name — GH_WorkflowStep → GH_RepoSecret / GH_OrgSecret (name match)",
       "is_traversable": false
     },
     {
       "name": "GH_UsesVariable",
-      "description": "[Workflow] Step references a variable by name — GH_WorkflowStep → GH_Variable (name match)",
+      "description": "[Workflow] Step references a variable by name — GH_WorkflowStep → GH_RepoVariable / GH_OrgVariable (name match)",
       "is_traversable": false
     }
   ],
@@ -801,4 +801,4 @@
     }
   ],
   "relationship_findings": []
-}
+}