Dataset: Commits from pull requests
Entity: Commit
Field ID: url
Type: Text
Description: The URL of the commit in the source application.
Source: App
From: |
|
Github (Commits) |
|
Gitlab (Commits) |
|
Bitbucket (Commits) |
|
Azure DevOps (Commits) | Built from |
Jira | N/A |
ClickUp | N/A |
Trello | N/A |
Reporting Use Cases
The Url field from the Commits dataset provides a direct, clickable link to the specific commit in its source Git platform (e.g., GitHub, GitLab). Its most critical function in reporting is to provide direct access to the code, turning high-level data into actionable insights.
Enabling Drilldowns and Investigation: This is the field's most important use. When you create an aggregated widget, such as a chart of "Commits per Day," and drill down into a specific data point, the resulting list of individual commits should always include the
Urlas a dimension. This transforms the report into an actionable tool, allowing developers to jump from a high-level trend directly to the line-by-line code changes with a single click.Providing Context in Lists: In any report that lists individual commits, including the
Urlprovides essential context and a direct path for further investigation, making the report far more useful for developers and managers alike.Filtering by Source Platform: You can also use the URL's structure to filter your reports by its source. For example, a filter like
Url ~ "github.com"will create a widget that only shows commits from your GitHub repositories, allowing you to analyze activity on a per-platform basis. Note, however, that using theSource Appfield is generally a better alternative for this use case.