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

gitip

v1.0.2

Published

auto generate git issue and pull request

Downloads

4

Readme

Installation

#not install
npx gitip

#install
npm install -g gitip
gitip

Before start

  • please make the fork branch first.

env-file

// <<required varibales>>

// Basically it uses an env file according to a "NODE_ENV" varibale.
// If your environment is "development", then gitip uses the target env file.
// If there isn't, a default file is ".env"

GIT_ACCESS_TOKEN = git access token.
REMOTE_REPO_OWNER = the name of remote branch owner
FORK_REPO_OWNER = the name of fork branch owner
REPO_NAME = the repository name;
BRANCH_NAME = the base(destination) branch name
TEMPLATE_TITLE_PLACEHOLDER = (optional) issue template title placeholder

If you want to use your template, you should set the TEMPLATE_TITLE_PLACEHOLDER varibale on your .env file. It will uses that variable as an issue title placeholder.

usage

🖊️ 1. create an issue

auto-issue

🖊️ 2. create a pull request

First of all, you need to commit your change

And, just select "create a pull request"

  • the title of a pull request comes from the latest commit
  • the body of a pull request comes from the latest commit either
  • If the pull request closed, it would close the issue together

auto-pr pr-result

⚠️ Caveat If you want to use "close" keyword to close related issue together, the base(destination) branch should be a default branch

default-branch

🖊️ 3. Synchronize a fork branch with origin branch

If you need to update your fork branch whenever origin is updated, you can do it without visiting to your fork branch manually

😩 Not this

sync-unrecommanded

😀 But this

sync-recommended

🖊️ 4. Remove unused issue branches

When you are using gitip, maybe you would face the situation that there are bunch of redundant issue branches like below

1. 😩 local debris

local-issue-debirs

2. 😩 fork debris

local-issue-debirs

If you should remove the unused branches, it takes time and effort. So, for you, you can remove them all at once like below

4. 😀 like this

clean-issue-branches

As a result, you meat the erased clean space

issue-clean issue-clean