Contribflow is a suite of high-level repository operations for making open source contributions easier. It's based on the git-flow branching model with modifications for the open souce workflow.
Want to see pretty graphs? Log in now!
npm install contribflow
|7||downloads in the last day|
|52||downloads in the last week|
|205||downloads in the last month|
|Last Published By|
|Version||0.3.7 last updated 10 months ago|
|Dependencies (7)||prompt, github, findup-sync, moment, shelljs, colors, semver|
Contribflow is a set of command-line operations that aims to make the contribution process easier for both contributors and repository managers.
- Easily create/delete git branches for new changes (a best-practice when contributing)
- Submit Github pull requests from the command-line
- Learn the underlying git commands as you go
For project owners:
- Allow git novices to more easily contribute while also learning git
- Prevent pull requests to the wrong branch
- Accept pull requests, squash commits, bump version, and update the changelog, all with a single command
Install the module globally with:
[sudo] npm install -g contribflow
This will make the
contrib command available to use in any project directory.
contrib command will run a series of git or github commands, and may prompt the user for more info. All git commands are printed as they are run, to encourage learning of the underlying git process.
feature or hotfix
There are two main branch types that contribflow is meant to work with, based largely on the Gitflow branching model.
- Feature: Any feature/change/fix that should go out with the next release. A new feature branch is based on the development branch--the branch with all the latest changes to the code base.
- Hotfix: An URGENT fix that should be applied and immediately deployed/released. A hotfix branch is based on the release branch (often called production or stable) and when finished is merged back into both the release branch (to be deployed) as well as the development branch.
In these examples
feature is used, but these same commands will work with
When starting a new feature you run the command:
contrib feature start
First, this will ask you to name your new feature (use letters, numbers and dashes). Next, it will run a series of git commands to create a new feature branch named "feature/[name-of-feature]." You'll work in this git branch, creating git commits as needed, until you're ready to submit a pull request to the upstream project. At this point you'll run:
contrib feature submit
This will create a pull request from your feature branch to the development branch of the upstream project.
At this point the project owner may ask you to make changes. To update your pull request you simply make the changes, commit them and
git push them up to the remote copy of your feature branch (remote tracking of the branch is set up when you start the feature). This will update your pull request.
Once the owner has accepted your pull request, you can clean up your feature branch. PLEASE NOTE: THIS WILL DELETE YOUR COPY OF THE FEATURE. This is meant to clean up your local and remote branches, so make sure any changes you don't want to lose have been pulled into the parent project or another branch first.
Run the command:
contrib feature delete
Copyright (c) 2013 Steve Heffernan Licensed under the Apache-2.0 license.