Skip to content
GitLab
Next
    • GitLab: the DevOps platform
    • Explore GitLab
    • Install GitLab
    • How GitLab compares
    • Get started
    • GitLab docs
    • GitLab Learn
  • Pricing
  • Talk to an expert
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
    Projects Groups Topics Snippets
  • Register
  • Sign in
  • GitLab GitLab
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
    • Locked files
  • Issues 52,741
    • Issues 52,741
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 1,552
    • Merge requests 1,552
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Artifacts
    • Schedules
    • Test cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GitLab.orgGitLab.org
  • GitLabGitLab
  • Issues
  • #33368
Closed
Open
Issue created Oct 03, 2019 by Jason D'Amour@jason.damour

Built in badge for releases

Problem to solve

Gitlab only offers 2 badges: pipeline and code coverage. Theres a lot more to a project then those two aspects, and there should be more badges to reflect that. The first I suggest is a Latest Release badge

Intended users

Proposal

Opening a merge request to create the badge. Will follow the same pattern as the pipeline badge and coverage

for example: https://img.shields.io/badge/Latest%20Release-v10.3.4-blue

The 2 fields required for badges is "Image url" and "Link". The image url will look like https://gitlab.com/%{project_path}/badges/release.svg and link will be https://gitlab.com/%{project_path}/releases

Permissions and Security

The badge should work for private repos as well as public. This is the reason gitlab should provide these badges: so that granting access to external badge generators isn't required.

Documentation

https://docs.gitlab.com/ee/user/project/badges.html

Testing

What does success look like, and how can we measure that?

What is the type of buyer?

Links / references

Release notes

We have added a new badge so you can easily see your latest release.

Edited Feb 17, 2022 by Chris Balane
Assignee
Assign to
Time tracking