An open API service indexing awesome lists of open source software.

https://github.com/joeyespo/github-version-tags

Displays the latest version of a project next to the repo name on GitHub.
https://github.com/joeyespo/github-version-tags

chrome-extension dependencies github productivity tools

Last synced: 10 months ago
JSON representation

Displays the latest version of a project next to the repo name on GitHub.

Awesome Lists containing this project

README

          

GitHub Version Tags
===================

![Current version on the Chrome Web Store](https://img.shields.io/badge/chrome%20web%20store-1.1.0-blue.svg "Current version on the Chrome Web Store")

Displays the latest version of a project next to the repo name on GitHub.

![Screenshot](media/screenshot.png "Screenshot")

Features
--------

- Displays the latest semantic version tagged in the repo in gray
- Displays the next pre-release (if available) in yellow
- Displays all versions on mouse hover

Installation
------------

![Try it now](media/tryitnowbutton.png "Click here to install from the Chrome Web Store")

Or manually:

1. Download or `git clone http://github.com/joeyespo/github-version-tags.git`
2. Open Chrome extensions and click on the `Load unpacked extension` button
3. Select the downloaded directory

How it works
------------

The extension requests the tags of the current repo from [the public GitHub API](https://developer.github.com/v3/repos/#list-tags),
performs a semver-sort (which supports the optional `v` prefix), and inserts
a `` next to the name. This is then cached until you leave the repo.

For private repos, it parses the tags from the `Switch branches/tags` dropdown.
This isn't as reliable since that HTML isn't on every page, but since you're
likely to want to see more versions of public repos than your own personal or
company repos, this keeps the project simple and avoids the auth concern.

Contributing
------------

1. Check the open issues or open a new issue to start a discussion around
your feature idea or the bug you found
2. Fork the repository and make your changes
3. Open a new pull request

If your PR has been waiting a while, feel free to [ping me on Twitter](http://twitter.com/joeyespo).