Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Snapcraft Last updated #10300

Open
MichaelHinrichs opened this issue Jun 26, 2024 · 3 comments
Open

Snapcraft Last updated #10300

MichaelHinrichs opened this issue Jun 26, 2024 · 3 comments
Labels
good first issue New contributors, join in! service-badge Accepted and actionable changes, features, and bugs

Comments

@MichaelHinrichs
Copy link

📋 Description

Snapcraft
Last updated | 21 June 2024

🔗 Data

IDK, however it is that the existing Snapcraft version badge works.

🎤 Motivation

It's like the other "Last Updated" badges.

@MichaelHinrichs MichaelHinrichs added the service-badge Accepted and actionable changes, features, and bugs label Jun 26, 2024
@chris48s
Copy link
Member

Snapcraft exposes a released-at property.
I'd probably frame this one in terms of release date rather than "last update".
This is exposed at the track / risk level so would need those params like the snapcraft version badge.

@chris48s chris48s added the good first issue New contributors, join in! label Jun 27, 2024
@abdullateef97
Copy link

@chris48s I'd like to work on this, how do I get started

@chris48s
Copy link
Member

chris48s commented Jul 29, 2024

There is a tutorial for adding new badges at https://github.com/badges/shields/blob/master/doc/TUTORIAL.md
The code for the existing snapcraft version badge is at https://github.com/badges/shields/tree/master/services/snapcraft
You might also find it useful to refer to the PR adding that badge at #9976

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue New contributors, join in! service-badge Accepted and actionable changes, features, and bugs
Projects
None yet
Development

No branches or pull requests

3 participants