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

@e-group/git-flow-cli

v2.1.2

Published

**git-flow-cli document**

Downloads

16

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

egroupteamegroupteamjerry_pjerry_p

Keywords

Readme

git-flow-cli

git-flow-cli document

Outline

  1. Overview
  2. Get Started
  3. create branch
  4. finish current branch
  5. prepare to prerelease

Overview

This project's main purpose is to let programmers don't need to handle with complex git stuff.

Our flow basic following the github-flow but the only difference is that we have a prerelease branch inorder to deploy to testing server.

The reason we don't deploy in develop branch is that we still have some config need modify manually.

Get Started

yarn add @e-group/git-flow-cli -D

Or

npm i @e-group/git-flow-cli -D

create branch

Create a new branch, which includes following choice.

  1. bug, Create a branch from master branch with bug prefix name.
  2. feature, Create a branch from master branch with feature prefix name.
  3. refactor, Create a branch from master branch with refactor prefix name.
  4. hotfix, Create a branch from master branch with hotfix prefix name.

finish current branch

If bug fixed or feature done which includes any version update can use this option.

Notice: Refactors will not update version. Hotfixs will merge into both master and prelease branch but with different version.The different is that master branch have the same behavior as bug branch but prelease branch add hotfix suffix.

prepare to prerelease

This option is use to merge master branch into prerelease branch. We highly recommend deploy prerelease branch in testing server but this is totally optional.