Skip to main content

Issues and PRs > Head ref | Repository

Tom Williams avatar
Written by Tom Williams
Updated over a week ago

Dataset: Issues & Pull Requests

Entity: Pull Requests, Issues

Field ID: head_ref_repository

Type: Text

Description: The repository of the head ref (source repository).

Source: App

Transformation logic: N/A

From:

Github (PRs, Issues)

head_repository.name_with_owner

Gitlab (PRs, Issues)

source.path_with_namespace

Bitbucket (PRs)

source.repository.full_name

Azure DevOps (PRs, Issues)

forkSource.repository

JIRA (Issues)

N/A

ClickUp (Issues)

N/A

Trello (Issues)

N/A

Reporting Use Cases

The Head Ref Repository field is particularly powerful for projects that accept contributions from forks, such as open-source software or projects involving external contractors. It allows you to distinguish between internal work and contributions from the wider community.

  • Filtering to Isolate Contribution Type: You can easily scope your reports to show either internal-only or external-only contributions (depending on your forking model).

    • External Contributions: To see all pull requests originating from forks, use a filter where head_ref_repository != base_ref_repository. This is invaluable for community management and understanding external engagement.

    • Internal Contributions: Conversely, to analyze only the work done by your core team within the main repository, you can filter where head_ref_repository == base_ref_repository.

  • Reporting on Community Engagement: When used as a dimension, this field helps you identify your most active external contributors and projects.

    • A bar chart with Head Ref Repository as the dimension and COUNT() as the metric can show which forked repositories are submitting the most pull requests, helping you recognize key community members.

  • Custom Formulas for High-Level Categorization: The most powerful use of this field is to create a simple, high-level breakdown of your development activity.

    • Internal vs. External Work: You can create a pie chart showing the proportion of work coming from your internal team versus external contributors. To do this, use a custom formula in a dimension like IF(head_ref_repository == base_ref_repository, "Internal", "External"). This provides a clear, at-a-glance view of your project's collaboration model.

Did this answer your question?