npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

gitlab-checker

v0.1.4

Published

Command line utility for performing some gitlab checks

Downloads

5

Readme

gitlab-checker

Command line utility that uses the gitlab API to check your repo branches and tags.

What?

The gitlab-checker utility looks for all your starred repositories on the gitlab host. It filters out any projects you do not have write access to. It's gonna retrieve all branches, tags, and open merge requests. For each branch it finds, it will extract the version from the file package.json.

Once it has fetched all info, it will evaluate the details. The #master and #develop branch get special treatment, they represent your stable and unstable branches. Any other branches are treated as feature branches (or bugfix branches, it doesn't matter).

It may conclude the following:

  • clean: This means #master, #develop and the latest tag are at the same commitId. Apart from feature branches, there are no changes that have not been released (tagged).
  • pending release: The #master and #develop branch are at the same commitId, but the latest tag is not at this commitId. There are no changes, but since there is no tag yet a release is still pending.
  • stable: The #master branch and latest tag are at the same commitId.
  • unstable: Code is present in #develop that is not yet merged to #master. Development is in progress, but since the changes are not merged to #master it is not yet being released.
  • unaligned: Everything is different. The latest tag is at a different commitId than #master, and #master is at a different commitId than #develop. This state should only occur during heavy developments (i.e. pushes to #develop) while a release is being created (which means tagging #master and thus aligning the commitId of the tag and #master).

Next to this, it will show you the current list of branches, any open merge requests, and will list the current version from package.json.

Installing

For convenience, install it globally, but it's not required. Settings are saved per installation (i.e. a global install will have a globally stored config, a local install wil have a locally stored config).

# global
$ npm install -g gitlab-checker

# local
$ npm install gitlab-checker

Usage

It'll ask for your details on first run and provide you the option to save them.

Note that there's no encryption going on, things are saved in plaintext within the module folder.

You can get your gitlab token from your gitlab account (see /profile/account on your gitlab host).

$ gitlab-checker

# which results in:
prompt: Enter the Gitlab host (including protocol):  https://your.gitlab.host
prompt: Provide your private token:  YOURGITLABPRIVATETOKEN
prompt: Store repo configuration? (y/n):  y

Options

  • --help: Shows a quick readme
  • --clearConfig: removes stored config