You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Exactly the same as the already existing "GitHub tag (latest by date)" badge, but for a GitLab.com repository.
e.g. "tag | v1.3.0"
🔗 Data
The data can be obtained from the public GitLab API (no key required). The call would be as follows: https://gitlab.com/api/v4/projects/{user}%2F{repo}/repository/tags
(where {user} and {repo} should be replaced by their respective values)
The response is a JSON array that is by default sorted with the latest tag on top, so the value could be extracted as: result[0].name
It can be used anywhere people are already using the equivalent GitHub badge, but for GitLab repositories. The main use case is to display the latest version of the app according to the repository.
In my case I want it alongside the F-Droid version badge so that it is clear whether the version that is published to F-Droid is the latest or not.
The text was updated successfully, but these errors were encountered:
📋 Description
Exactly the same as the already existing "GitHub tag (latest by date)" badge, but for a GitLab.com repository.
e.g. "tag | v1.3.0"
🔗 Data
The data can be obtained from the public GitLab API (no key required). The call would be as follows:
https://gitlab.com/api/v4/projects/{user}%2F{repo}/repository/tags
(where
{user}
and{repo}
should be replaced by their respective values)The response is a JSON array that is by default sorted with the latest tag on top, so the value could be extracted as:
result[0].name
The documentation for the call can be found here.
🎤 Motivation
It can be used anywhere people are already using the equivalent GitHub badge, but for GitLab repositories. The main use case is to display the latest version of the app according to the repository.
In my case I want it alongside the F-Droid version badge so that it is clear whether the version that is published to F-Droid is the latest or not.
The text was updated successfully, but these errors were encountered: