Skip to content
GitLab
Next

Better display of tags in commits list view

Second, we will see a better display of tags in the commits list view. Identifying tagged commits helps to locate important events in a project. It is currently not possible to see tags in the commits list view. We will be enabling this in %15.8.

Release post

Identifying commits that have been tagged just got simpler. You now find these tags also in the commits list under Repository > Commits. This may help to see what has been committed since a particular tagged release commit.

image

Problem to solve

Identifying tagged commits is important to locate important events in a project. It is currently not possible to see tags in the commits list, causing extra work to identify which tag is connected to a particular tag.

Current commit list Screen_Shot_2019-06-07_at_2.59.08_PM

Proposal

  • Show tags that match each commit in the commits view (commits/<branch>)
    • Maybe we want to explain that match (or whatever word we use) is like doing git tag --points-at <object> where <object> is the commit (see docs).
  • When multiple tags match, display text as Multiple tags
    • To view the multiple tags, users will need to click on the commit to view the commit/<SHA>detail view. Expanding the tags inline in the list view may work for a handful of tags but in the extreme case it might not (example: commit with many tags)
    • Initially we were planning to display {#} tags where # is the number of matched tags but for performance reason we went with "Multiple tags" #18795 (comment 1231049433)
    • Displaying the tags in a tooltip is a possibility that we can explore in a future iteration.
  • Badge details

we could iterate to have the user click the "5 tags" and see the 5 tags in place without having to go to the commit? (we could probably create an issue for that). If so, backend providing us with the actual tags could prepare us for that iteration later.

#18795 (comment 1208237323)

The API would return all matching tags and the UI will be responsible for the display logic.

image

Use cases

Any repository with many branches (like one per developer) and tags (like one per daily build).

Customers

customer contact
https://gitlab.my.salesforce.com/0016100001F2Gsw @apham4
https://gitlab.my.salesforce.com/0016100000Nm6rw @bmiller1
https://gitlab.zendesk.com/agent/tickets/269185  @myacksmith
https://gitlab.zendesk.com/agent/tickets/288486 @arihantar
https://gitlab.my.salesforce.com/0014M00001nJiRm @bmiller1
https://gitlab.my.salesforce.com/0016100000QmcO1 @bgadberry

Interviews

https://docs.google.com/document/d/1AFMVZK8sK8xgEcPqGdlEidZSG2dcjbIEnN0MIcPJJaQ/edit#

This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.

Availability and Testing

Ensure an adequate test coverage for tagged commits. In addition to stubbed tests it would be beneficial to add an E2E test for adding and verifying tags in commits list view (created gitlab-org/quality/quality-engineering/team-tasks#1609 (closed)).

Edited by Torsten Linz