Skip to main content

Commits > Updated at

Written by Tom Williams

Dataset: Commits from pull requests

Entity: Commit

Field ID: updated_at

Type: Datetime

Description: The datetime at which the commit was last updated. A commit cannot be changed once created, so this is always the same as Created at.

Source: App

App Mapping

Github (Commits)

commit.committedDate

Gitlab (Commits)

created_at

Bitbucket (Commits)

Cloud

date

Data Center

authorTimestamp (the author date)

Azure DevOps (Commits)

committer.date

Jira

N/A

ClickUp

N/A

Trello

N/A

Reporting Use Cases

The Updated at field of a commit is taken from the source application, not from Keypup's import. Since commits in Git are immutable (rebasing or amending a commit creates a new one), this field holds the same value as Created at and is rarely useful on its own.

  • Use Created at instead: For all standard development reports, such as tracking commit frequency or analyzing work patterns, use the Created at field. It gives the same result and says what it measures.

  • Not a synchronization indicator: This field does not tell when Keypup last imported a commit. A filter like Updated at in the previous 1 hour returns the commits created in the last hour, not the commits recently synchronized, and a formula like updated_at - created_at always returns 0.

Did this answer your question?