> ## Documentation Index
> Fetch the complete documentation index at: https://bloodhound.specterops.io/llms.txt
> Use this file to discover all available pages before exploring further.

# GH_HasBranch

> Repository has this branch

<img noZoom src="https://mintcdn.com/specterops/tTIczgde9H07oLXf/assets/enterprise-AND-community-edition-pill-tag.svg?fit=max&auto=format&n=tTIczgde9H07oLXf&q=85&s=ad49a576589f4d2a8081df77d07fdf56" alt="Applies to BloodHound Enterprise and CE" width="482" height="45" data-path="assets/enterprise-AND-community-edition-pill-tag.svg" />

## Edge Schema

* Source: [GH\_Repository](/opengraph/extensions/github/nodes/gh_repository)
* Destination: [GH\_Branch](/opengraph/extensions/github/nodes/gh_branch)
* Traversable: ❌

## General Information

The non-traversable GH\_HasBranch edge represents the relationship between a repository and its branches. This edge links each collected branch to its parent repository. It is a structural edge that provides the foundation for understanding branch-level protections and access controls. While not traversable itself, it connects repositories to branches where traversable edges like [GH\_CanWriteBranch](/opengraph/extensions/github/edges/gh_canwritebranch) and [GH\_CanEditProtection](/opengraph/extensions/github/edges/gh_caneditprotection) model the effective access.

```mermaid theme={null}
graph LR
    node1("GH_Repository GitHound")
    node2("GH_Branch main")
    node3("GH_Branch develop")
    node4("GH_Branch feature/auth")
    node1 -- GH_HasBranch --> node2
    node1 -- GH_HasBranch --> node3
    node1 -- GH_HasBranch --> node4
```