Dataset: Commits from pull requests
Entity: Commit
Field ID: updated_at
Type: Datetime
Description: The datetime at which the commit was last updated.
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 Updated At field from the Commits dataset is a system-level timestamp that reflects the last time Keypup's record of the commit was updated. Since commits in Git are immutable, this field is not used for measuring development workflows but is instead valuable for data synchronization and auditing purposes.
Auditing Data Freshness: The primary use of this field is to verify that commit data is being actively synchronized into Keypup.
You can create a report to see all commits that have been recently processed by the system using a filter like
Updated At in the previous 1 hour. This is useful for confirming that your data is up-to-date.
Analyzing Sync Latency: You can measure the time difference between when a commit was created in Git and when it was last updated in Keypup's system.
A custom formula like
(updated_at - created_at) / HOUR()can calculate this "sync lag." While typically very short, a high value could indicate a delay during the initial import of a large repository.
Distinguishing from created_at: For all standard development reports, such as tracking commit frequency or analyzing work patterns, the
Created Atfield should always be used, as it represents the actual moment the code was written. TheUpdated Atfield is reserved for system-level data health checks.