--- title: Commits and task executions in DevOps description: Run commits in DevOps are associated to a task execution. locale: en-US canonical_url: https://www.servicenow.com/docs/r/australia/it-service-management/devops-change-velocity/commits-and-task-executions-in-devops.html release: australia product: DevOps Change Velocity classification: devops-change-velocity topic_type: concept last_updated: "2026-03-12" reading_time_minutes: 1 breadcrumb: [Manage, DevOps Change Velocity, IT Service Management] --- # Commits and task executions in DevOps Run commits in DevOps are associated to a task execution. For a commit to show up as a run commit, the commit record must exist in ServiceNow prior to the job/pipeline run. In the event that jobs are rerun on the same commit, these conditions apply. - Azure DevOps doesn’t show any run commits. - GitLab displays only the last commit as a run commit. - Jenkins displays only the last commit as a run commit on which it was run. The difference of all commits isn’t shown. Multiple commits in a single payload \(commit arrays\) have these limitations.
| Tool | Max commits per payload |
|---|---|
| Azure DevOps | - If the DevOps property **Enable whether Azure DevOps Run Commits must be determined from the last successful pipeline build** is enabled, DevOps Change will pick up the last commits, up to a maximum of 2000, created after the last successful pipeline build from Azure DevOps as part of Run Commits. - If disabled, only the last 200 commits will be considered for Run Commits. |
| GitHub | - If the DevOps property **Enable whether GitHub Run Commits must be determined from the last successful workflow run** is enabled, DevOps Change will pick up the first 2000 commits after the last successful workflow run in GitHub as part of Run Commits. - If disabled, only the last commit will be picked up for Run Commits. |
| GitLab | 20 |