badges/shields

Badge request: Userscript version

Open

#829 opened on Nov 6, 2016

View on GitHub
 (3 comments) (0 reactions) (0 assignees)JavaScript (5,423 forks)batch import
good first issueservice-badge

Repository metrics

Stars
 (22,337 stars)
PR merge metrics
 (Avg merge 6d 3h) (71 merged PRs in 30d)

Description

Since the dead of Userscripts.org a few years ago, a lot of script-writers moved their userscripts to GitHub. It would be great if there was a shield showing the @version 1 2 of an userscript. Other metadata would be great too. I also noticed that userscripts mostly don't live on the repos root, so navigating to the .user.js file should be part of the shield url.

Contributor guide

Research direction
Study existing badge implementations in the shields project to understand the pattern for creating a new badge. Then implement a badge that fetches a userscript file from a GitHub repository, parses the @version metadata, and displays it as a shield. Consider allowing custom paths to the .user.js file.
Tech stack
javascript
Domain
backendapi
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
3-5 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitJavaScript
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60