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

gijit

v2.1.4

Published

Show JIRA information for git branches

Downloads

408

Readme

Gijit

This tool loads JIRA information for your git branches, as long as your branches are named with the JIRA issue keys.

Installation

Install Gijit globally with the following.

$ npm install -g gijit

The very first time you invoke gijit it will ask for your atlassian host, username and an API Token, which you can obtain by visiting https://id.atlassian.com/manage/api-tokens. This information will be stored in your home folder as a file gijit.config.js.

$ gijit

Commands

gijit all

Show information for all local branches. The response will look like the following.

┌────────────┬─────────────────────────┬──────┬──────────┬─────────┬──────────┬─────────┬────────┐
│ Key        │ Summary                 │ Type │ Priority │ Status  │ Assignee │ Creator │ Labels │
├────────────┼─────────────────────────┼──────┼──────────┼─────────┼──────────┼─────────┼────────┤
│ DEV-5814   │ Create a get all page   │ Task │ Major    │ Open    │ foo.bar  │ baz.tar │ page   │
├────────────┼─────────────────────────┼──────┼──────────┼─────────┼──────────┼─────────┼────────┤
│ DEV-5975   │ Create a search feature │ Task │ Major    │ Open    │ foo.bar  │ baz.tar │ search │
├────────────┼─────────────────────────┼──────┼──────────┼─────────┼──────────┼─────────┼────────┤
│ DEV-6745 * │ Fix bug in show details │ Bug  │ Minor    │ Testing │ foo.bar  │ baz.tar │ detail │
└────────────┴─────────────────────────┴──────┴──────────┴─────────┴──────────┴─────────┴────────┘

gijit detail

This shows the detailed view for the JIRA item associated with the current branch.

gijit detail <issueKey>

Optionally you can pass a JIRA issue key, e.g. gijit detail DEV-1234, and it will show information for issue with key DEV-1234.

gijit search <jiraQuery>

This will return the search results for any JIRA query, for example gijit search 'assignee=foo.bar and status=open'

gijit open <issueKey>

This will open the issue corresponding to the current branch in the default browser. If issueKey is given it will open that issue in the default browser.

gijit comment

Show comments assocated with current branch

gijit comment -i <issueKey>

Show comments associated with issueKey

gijit comment -i <issueKey> -m <commentBody>

Add a comment to issue specified by issueKey, if not -i is not given then comment will be added to issue related with current branch

gijit comment -i <issueKey> -c <commentId> -m <commentBody>

Replace comment specified by commentId with new commentBody for issueKey

gijit user [<query>]

If no query is given show list of all users. If query string is provided, show users matching query string

Customization

You can customize how the items are rendered by editing the gijit.config.js file, and add a property called config. The following properties are allowed (and are the defaults).

// contents of gijit.config.js
module.exports = {
  host: /* host */,
  username: /* your username */,
  password: /* your API token. To get an API token visit https://id.atlassian.com/manage/api-tokens */,
  config: {
    colors: true, // enable/disable colors
    fields: {
      key: { color: "bold" }, // any of the chalk colors are allowed
      summary: { width: 80 },
      issuetype: { color: "cyan" },
      priority: { color: "magenta" },
      status: { color: "gray" },
      project: {},
      assignee: { color: "blue" },
      reporter: { color: "green" },
      creator: { color: "green" },
      created: { color: "dim" },
      updated: { color: "dim" },
      environment: { color: "dim" },
      labels: { color: "yellow", width: 30 },
      description: { width: 80 }
    },
    lineFields: [
      // fields to be displayed in the table for
      // `gijit all` and `gijit search` commands
      "key",
      "summary",
      "issuetype",
      "priority",
      "status",
      "assignee",
      "creator",
      "labels"
    ]
  }
}