Dataset: Commits from pull requests
Entity: Commit
Field ID: sha
Type: Text
Description: The SHA1 of the commit.
Git assigns each commit a unique ID, called a SHA or hash, that identifies:
The specific changes
When the changes were made
Who created the changes
Source: App
From: |
|
Github (Commits) |
|
Gitlab (Commits) |
|
Bitbucket (Commits) |
|
Azure DevOps (Commits) |
|
Jira | N/A |
ClickUp | N/A |
Trello | N/A |
Reporting Use Cases
The Sha1 field provides the unique cryptographic hash that serves as the definitive and universally recognized identifier for a specific commit. Its primary role in reporting is to provide precise context in detailed views and enable accurate drilldowns.
Context and Drilldown: This is the field's most critical function. In any drilldown report that lists individual commits, the
Sha1is the essential "ground truth" identifier. When you click on a metric representing "10 commits" and drill down, the SHA1 in the resulting list guarantees that you are seeing the exact 10 commits that make up that total. It provides an unambiguous reference that developers can copy and use directly in their Git client or command line.Filtering for Specific Commits: It is the most precise way to find and analyze a single commit if you know its hash.
To investigate a specific code change, you can use a filter like
Sha1 = "a1b2c3d4e5f6a7b8c9d0...".
Custom Formulas for Display: While not used for calculations, you can format it for better readability in reports.
For instance, you can create a "Short SHA" dimension for a list report with the custom formula
LEFT(sha, 7), which is a common convention for displaying commit hashes in a more compact form.