…hat they're the only lines that show.
…-no-verbose or set to false in git config (pivotal.verbose).
…Blocked: ". Makes it easier to identify when cards were blocked and for what reason. [contributes #7]
…s blocking a specific card given an id (rather then using the current branch). [contributes #7]
…in an acceptable state at least for bugs, chores, and features. [contributes #10]
…merge the topic branch into the main integration branch (e.g. master). [contributes #10]
…, pulls, merges topic branch into configured acceptance branch, and then pushes acceptance. * it no longer removes the topic branch, finishing just means the card is ready for review, once it's accepted it will be removed * uses git config setting 'acceptance-branch' to identify which branch to merge into after finishing a card [contributes #9]
…tal. [contributes #5]
…d git-feature. * Changing API of Commands::Base to not take STDIN/STDOUT in the constructor [contributes #1]
…aceholder CURRENT_CARD. Less placeholders to maintain and account for. [contributes #1]
…. Removing bug/chore/feature.feature [contributes #1]
…art in feature.feature. Also, removing pick.feature as its no longer needed. [contributes #1]
…votal api key, and the pivotal user rather than include them in all scenarios explicitly. [contributes #1]
…itive. [contributes #1]
…ute without being configured. [contributes #1]
* Starting the next feature interactively (without -D option) * Starting the next feature using configured defaults (with -D option) * Starting the next feature with explicit command line arguments Removing the test story in Pivotal and the need to have one existence before the feature file runs. [contributes #1]