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

ya-git-lab

v0.7.0

Published

Yet Another Git Extension for GitLab

Downloads

6

Readme

ya-git-lab

Yet Another Git Extension for GitLab

This is a node.js package that implements a git subcommand for integration with GitLab.

Installation

npm install -g ya-git-lab

Usage

$ git lab
NAME
        git-lab - GitLab integration

SYNOPSIS
        git lab start <issueid>
        git lab bump
        git lab done <issueid>
        git lab merge-train <mr-id>
        git lab open [<issue-id> | i<issue-id> | m<mr-id>]

DESCRIPTION
        This command facilitates using Git with GitLab. The following subcommands are available:

        start
                Use the start subcommand to start working on an issue. It starts the issue in GitLab
                and creates an appropriately named branch in your local git repository.

        bump
                Use the bump subcommand to create a new branch for the current issue, in preparation for rebasing.
                The first time this is done, it appends ".v1" to the issue name. On second and subsequent bumps
                the version numbers is bumped: .v2, .v3, etc.
                The bump subcommand does not change gitlab state.

        done
                Use the done command after your branch is merged to delete all branches associated with the issue

        merge-train
                The merge-train command requires a merge request ID. It creates a branch for the provisional merge commit
                if the train succeeds up through that MR. The branch will be named with the format
                `merge-train/${mr-id}-${commit}`, where commit is an abbreviated commitish for the merge commit.

        open
                The open command will open gitlab issue or merge request page in your default web browser.
                If no argument is provided, the issue for the current branch will be opened.
                An argument of the form `ID` or `iID` will open issue #ID.
                An argument of the form `mID` will open MR !ID.
                (You can also use "#ID" and "!ID", but only with quoting, because Bash treats both of these characters specially.)

CONFIGURATION
        You must set two git configuration variables:
            gitlab.token    A Personal Access Token that you create for API access via User Settings > Access Tokens.
            gitlab.project  The Project ID of your GitLab project displayed under Project > Details.
        You may optionally set:
            gitlab.master   The long-lived branch that serves as your master branch. git-lab will checkout this
                            branch when it deletes any branches with `git lab done <issueid>`.
            gitlab.types    If true, create branches with a prefix `<type>/` if the issue has a label `type::<type>`.
                            Supported types are `feature`, `bug`, `chore`, `epic`.
                            The default is false, i.e. do not prefix with the type.

Other similar packages

This package is derived from a similar package for Pivotal Tracker integration: ya-git-pivotal