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

gflow-cli

v0.0.5

Published

git flow cli

Downloads

2

Readme

gflow-cli

NPM version npm download license

A git flow cli using nodejs, which improve your efficiency.

gitflow png

Installation

npm i gflow-cli -g

Usage


FEATURE

:point_right: gflow feature start <feature_name>

This will do follows:

- git checkout develop
- git pull
- git checkout -B feature/<feature_name>
- git push

:point_right: gflow feature finish <feature_name>

This will do follows:

- git checkout develop
- git pull
- git merge feature/<feature_name>

:point_right: gflow feature publish <feature_name>

This will do follows:

- git checkout develop
- git pull
- git merge feature/<feature_name>
- git push
- git push origin :feature/<feature_name>

:warning: This will delete the remote branch feature/<feature_name>, but do not delete local feature branch.


RELEASE

:point_right: gflow release start <release_name>

This will do follows:

- git checkout develop
- git pull
- git checkout -B release/<release_name>
- git push

:point_right: gflow release finish <release_name>

This will do follows:

- git checkout master
- git pull
- git merge release/<release_name>

- git tag <release_name> master -f

- git checkout develop
- git pull
- git merge release/<release_name>
  • This will add a tag base master, named <release_name>, you can use --no-tag to avoid it.
  • You can also using -t <tag_name> or --tag <tag_name> to replace <release_name>.

:point_right: gflow release publish <release_name>

This will do follows:

- git checkout master
- git pull
- git merge release/<release_name>
- git push

- git tag <release_name> master -f
- git push --tags

- git checkout develop
- git pull
- git merge release/<release_name>
- git push
- git push origin :release/<release_name>

:warning:

  • This will delete the remote branch release/<release_name>, but do not delete local release branch.
  • This will add a tag base master, named <release_name>, you can use --no-tag to avoid it.
  • You can also using -t <tag_name> or --tag <tag_name> to replace <release_name>.

HOTFIX

:point_right: gflow hotfix start <name>

This will do follows:

- git checkout master
- git pull
- git checkout -B hotfix/<name>
- git push

:point_right: gflow hotfix finish <name>

This will do follows:

- git checkout master
- git pull
- git merge hotfix/<name>

- git tag <name> master -f

- git checkout develop
- git pull
- git merge hotfix/<name>
  • This will add a tag base master, named <hotfix_name>, you can use --no-tag to avoid it.
  • You can also using -t <tag_name> or --tag <tag_name> to replace <hotfix_name>.

:point_right: gflow hotfix publish <name>

This will do follows:

- git checkout master
- git pull
- git merge hotfix/<name>
- git push

- git tag <name> master -f
- git push --tags

- git checkout develop
- git pull
- git merge hotfix/<name>
- git push
- git push origin :release/<name>

:warning:

  • This will delete the remote branch hotfix/<name>, but do not delete local branch.
  • This will add a tag base master, named <hotfix_name>, you can use --no-tag to avoid it.
  • You can also using -t <tag_name> or --tag <tag_name> to replace <hotfix_name>.

BUGFIX

:point_right: gflow bugfix start <name>

This will do follows:

- git checkout develop
- git pull
- git checkout -B bugfix/<name>
- git push

:point_right: gflow bugfix finish <name>

This will do follows:

- git checkout develop
- git pull
- git merge bugfix/<name>

:point_right: gflow bugfix publish <name>

This will do follows:

- git checkout develop
- git pull
- git merge bugfix/<name>
- git push
- git push origin :bugfix/<name>

:warning: This will delete the remote branch bugfix/<name>, but do not delete local branch.