Skip to content

Git Commit Push Username

When commits are pushed to a Clarive-managed Git repository, the system now records the Clarive username of the person who performed the push alongside the standard Git author information.

How it works

Git commits contain a git author name (the person who wrote the code). However, when pushing to Clarive, the person doing the push authenticates via HTTP Basic Auth or API key. These are often different - for example, a CI/CD system may push commits authored by multiple developers.

Clarive now stores the authenticated push username on the GitRevision resource (CI) at the time of the push. This username is then displayed in two places:

Repository Commits Browser

In the Code > Repositories section, the commit list and commit detail views show the Clarive push username next to the git author name when they differ. This helps identify who actually pushed the code to Clarive.

  • Commit list: The push username appears after the git author name, separated by a dot
  • Commit detail: The push username appears in parentheses after the author, labeled "pushed by"

Topic Activity Timeline

In the topic activity timeline, each commit row now displays the git author name alongside the commit message and SHA. The Clarive push username is already shown at the bottom of each commit group via the existing event user display.

Notes

  • The push username is only recorded for new pushes. Existing GitRevision records created before this feature will not have a username until the next push that updates them.
  • If the git author name matches the Clarive push username, the push username is not displayed separately to avoid redundancy.