Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Documented init -d flag and feature publish/pull #178

Merged
merged 2 commits into from
Feb 13, 2012
Merged

Documented init -d flag and feature publish/pull #178

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
5a58633
Documented init -d flag and publish/pull
Dec 20, 2011
905cfb1
whitespace
Dec 20, 2011
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 8 additions & 1 deletion README.mdown
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -83,13 +83,15 @@ in a Github fork, of course.

To initialize a new repo with the basic branch structure, use:

git flow init
git flow init [-d]

This will then interactively prompt you with some questions on which branches
you would like to use as development and production branches, and how you
would like your prefixes be named. You may simply press Return on any of
those questions to accept the (sane) default suggestions.

The ``-d`` flag will accept all defaults.


### Creating feature/release/hotfix/support branches

Expand All @@ -101,6 +103,11 @@ those questions to accept the (sane) default suggestions.

For feature branches, the `<base>` arg must be a commit on `develop`.

* To push/pull a feature branch to the remote repository, use:

git flow feature publish <name>
git flow feature pull <remote> <name>

* To list/start/finish release branches, use:

git flow release
Expand Down