gittyup 1.0.3

data/.gitignore

@@ -0,0 +1,17 @@
+*.gem
+*.rbc
+.bundle
+.config
+.yardoc
+Gemfile.lock
+InstalledFiles
+_yardoc
+coverage
+doc/
+lib/bundler/man
+pkg
+rdoc
+spec/reports
+test/tmp
+test/version_tmp
+tmp

data/Gemfile

@@ -0,0 +1,4 @@
+source 'https://rubygems.org'
+
+# Specify your gem's dependencies in gittyup.gemspec
+gemspec

data/LICENSE.txt

@@ -0,0 +1,22 @@
+Copyright (c) 2013 Paul Morganthall
+
+MIT License
+
+Permission is hereby granted, free of charge, to any person obtaining
+a copy of this software and associated documentation files (the
+"Software"), to deal in the Software without restriction, including
+without limitation the rights to use, copy, modify, merge, publish,
+distribute, sublicense, and/or sell copies of the Software, and to
+permit persons to whom the Software is furnished to do so, subject to
+the following conditions:
+
+The above copyright notice and this permission notice shall be
+included in all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
+EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
+MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
+NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE
+LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION
+OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION
+WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

data/README.md

@@ -0,0 +1,76 @@
+## introduction
+
+New users to **git** and **Heroku** sometimes have trouble
+with the syntax and arguments of the git commands required
+to deploy an application to Heroku. This wrapper combines
+the git *add*, *commit*, and *push* commands.
+
+The command has no arguments. The user is prompted for a
+commit message. The wrapper contains no error handling,
+so the user will receive standard errors from git.
+
+## installation
+If you have a Gemfile, add **gittyup**. Otherwise, install it like this:
+
+    $ gem install gittyup
+
+## usage
+
+typical usage:
+
+    $ gittyup
+    enter commit message (blank to exit)> New site title
+    [master 318bd11] New site title
+     1 files changed, 2 insertions(+), 0 deletions(-)
+
+*wait for push to start, then*
+
+*lots of messages from Heroku*
+
+*until the push ends like this*
+
+    To git@heroku.com:awesomeproject.git
+       13f987c..aceaf78  master -> master
+    $
+
+## detailed operation
+All code is in [bin/gittyup](https://github.com/slothbear/gittyup/blob/master/bin/gittyup).
+An error from any system command causes the script to exit.
+
+Since the script is designed for beginning users, it assumes
+you are committing to and pushing the **master** branch.
+If you know enough to have multiple
+branches, you probably don't need this script.
+
+The script performs these steps:
+
+1. `git status` If this command fails, the current directory is
+probably not a git repository.
+1. `git status` If this command provides no output, then there
+are no changed files to commit.
+1. `git add --all` Add new, changed, and removed files to the index.
+1. Prompt the user for a commit message. If no message is entered, the script exits.
+1. `git commit --message <message>` Record changes to the repository.
+1. `git push heroku master` Deploy the updated repository to Heroku.
+
+For every system command performed, the exit status of the
+operation is passed back via `exit $?.exitstatus`. The status
+
+## tests
+A nicely formatted test suite is available at
+[Relish](http://relishapp.com/slothbear/gittyup).
+
+To run the tests:
+```
+    $ cd gittyup
+    $ bundle
+    $ rake
+```
+
+## contributing
+
+1. Fork it
+2. Create your feature branch (`git checkout -b my-new-feature`)
+3. Commit your changes (`git commit -am 'Add some feature'`)
+4. Push to the branch (`git push origin my-new-feature`)
+5. Create new Pull Request

data/Rakefile

@@ -0,0 +1,13 @@
+require 'bundler'
+require 'cucumber'
+require 'cucumber/rake/task'
+
+Bundler::GemHelper.install_tasks
+
+Cucumber::Rake::Task.new(:features) do |t|
+  t.cucumber_opts = "features --format pretty -x"
+  t.fork = false
+end
+
+task :default => 'features'
+

data/bin/gittyup

@@ -0,0 +1,29 @@
+#!/usr/bin/env ruby
+require 'readline'
+
+# Perform git add, commit, and push to Heroku.
+
+status_command = 'git status --porcelain'
+puts "\nChecking git status with: #{status_command}"
+status = %x[#{status_command}]
+exit $?.exitstatus unless $?.success?
+
+if status.empty?
+  puts '** No files have been changed, created, or removed.'
+  exit 1
+end
+
+git_add_command = 'git add --all'
+puts "\nStaging files for commit with: #{git_add_command}"
+exit $?.exitstatus unless system(git_add_command)
+
+message = Readline.readline('enter commit message (blank to exit)> ')
+git_commit_command_args = ['git', 'commit', '--message', message]
+puts "\nCommiting files with: #{git_commit_command_args.join(' ')}"
+exit $?.exitstatus unless system(*git_commit_command_args)
+
+git_push_command = 'git push heroku master'
+puts "\nPushing to heroku with: #{git_push_command}"
+system 'git push heroku master'
+exit $?.exitstatus
+

data/features/adcopu.feature

@@ -0,0 +1,46 @@
+Feature: Combine git add, commit, and push into one command
+  As an aspiring web developer with little 'git' experience
+  I want to deploy my changes to Heroku with one command
+  So that everyone in the world can see them
+
+Scenario: Successfully add, commit, and (fake) push
+  Given a git repository with pending changes
+  And there is a git remote named heroku
+  When I run `gittyup` interactively
+  And I type "more golden retriever puppies"
+  # This is not a successful push, but it does talk to Heroku.
+  # TODO: the push requires prior Heroku auth setup.
+  Then the output should contain "No such app"
+  And the exit status should not be 0
+
+Scenario: The git repository does not exist
+  Given a blank directory
+  When I run `gittyup`
+  Then the exit status should not be 0
+  And the output should contain "Not a git repository"
+
+Scenario: No files changed (nothing to commit)
+  Given an initialized git repository
+  When I run `gittyup`
+  Then the exit status should not be 0
+  And the output should contain "No files have been changed"
+
+Scenario: Errors from git add
+  # The exit code from git add could be non-zero if there were
+  # errors adding files to the index. How to test?
+
+Scenario: Cannot commit without commit message
+  Given a git repository with pending changes
+  When I run `gittyup` interactively
+  And I type ""
+  Then the output should contain "empty commit message"
+  And the exit status should not be 0
+
+Scenario: Cannot push without a remote named 'heroku'
+  Given a git repository with indexed changes
+  But there is no remote named heroku
+  When I run `gittyup` interactively
+  And I type "railsbridge workshop changes"
+  Then the exit status should not be 0
+  And the output should contain "'heroku' does not appear"
+

data/features/readme.md

@@ -0,0 +1,7 @@
+New users to git and Heroku sometimes have trouble with the syntax of
+the git commands required to deploy an application to Heroku. This
+wrapper combines the git add, commit, and push commands needed.
+
+The command has no arguments. The user is prompted for a commit message.
+The wrapper contains no error handling, so the user will receive errors
+from git.

data/features/step_definitions/adcopu_steps.rb

@@ -0,0 +1,41 @@
+Given /^a blank directory$/ do
+  blank_directory
+end
+
+Given /^an initialized git repository$/ do
+  blank_directory
+  run 'git init'
+end
+
+Given /^a git repository with pending changes$/ do
+  blank_directory
+  run 'git init'
+  write_file('railsbridge-boston.rb', '')
+end
+
+Given /^a git repository with indexed changes$/ do
+  blank_directory
+  run 'git init'
+  write_file('railsbridge-boston.rb', '')
+  run 'git add -all'
+end
+
+Given /^there is no remote named heroku$/ do
+  run_simple(unescape('git remote rm heroku'), false)
+end
+
+Given /^there is a git remote named heroku$/ do
+  # The only the step that uses the heroku remote needs more time.
+  # Tried 'run for up to 15 seconds', still failed at 3 seconds.
+  @aruba_timeout_seconds = 15
+
+  steps %Q{
+    Given I successfully run `git remote add heroku git@heroku.com:gittyup_test_app.git`
+  }
+end
+
+def blank_directory
+  create_dir('repository')
+  cd('repository')
+end
+

data/features/support/env.rb

@@ -0,0 +1,16 @@
+require 'aruba/cucumber'
+
+Before do
+  # The default ./tmp/aruba directory can't be used because it is a 
+  # subdir of the gem directory, already part of a git repository.
+  # We are responsible for cleaning the directory on startup.
+  # Being careful, we only clean items we know we created.
+  temp_dir = '/tmp/aruba/gittyup/'
+  FileUtils.rm_rf(temp_dir + 'repository/.git', :secure => true)
+  FileUtils.rm_f(temp_dir + 'repository/railsbridge-boston.rb')
+  FileUtils.rmdir(temp_dir + 'repository')
+  FileUtils.rmdir(temp_dir)
+
+  @dirs = [temp_dir]
+end
+

data/gittyup.gemspec

@@ -0,0 +1,28 @@
+# -*- encoding: utf-8 -*-
+lib = File.expand_path('../lib', __FILE__)
+$LOAD_PATH.unshift(lib) unless $LOAD_PATH.include?(lib)
+require 'gittyup/version'
+
+Gem::Specification.new do |gem|
+  gem.name          = "gittyup"
+  gem.version       = Gittyup::VERSION
+  gem.authors       = ["Paul Morganthall"]
+  gem.email         = ["pcm@morganthall.com"]
+  gem.description   = %q{New users to git and Heroku sometimes have trouble
+                         with the syntax of the git commands required to deploy
+                         an application to Heroku. This wrapper combines
+                         the git add, commit, and push commands needed. The
+                         command has no arguments. The user is prompted for a
+                         commit message. The wrapper contains no error handling,
+                         so the user will receive errors from git.
+                         }
+  gem.summary       = %q{wrapper for git add/commit/push to Heroku}
+  gem.homepage      = "http://github.com/slothbear/gittyup"
+
+  gem.files         = `git ls-files`.split($/)
+  gem.executables   = gem.files.grep(%r{^bin/}).map{ |f| File.basename(f) }
+  gem.test_files    = gem.files.grep(%r{^(test|spec|features)/})
+  gem.require_paths = ["lib"]
+
+  gem.add_development_dependency('aruba', '~> 0.5.1')
+end

data/lib/gittyup.rb

@@ -0,0 +1,5 @@
+require "gittyup/version"
+
+module Gittyup
+  # Your code goes here...
+end

data/lib/gittyup/version.rb

@@ -0,0 +1,3 @@
+module Gittyup
+  VERSION = "1.0.3"
+end

metadata

@@ -0,0 +1,85 @@
+--- !ruby/object:Gem::Specification
+name: gittyup
+version: !ruby/object:Gem::Version
+  version: 1.0.3
+  prerelease: 
+platform: ruby
+authors:
+- Paul Morganthall
+autorequire: 
+bindir: bin
+cert_chain: []
+date: 2013-02-22 00:00:00.000000000 Z
+dependencies:
+- !ruby/object:Gem::Dependency
+  name: aruba
+  requirement: !ruby/object:Gem::Requirement
+    none: false
+    requirements:
+    - - ~>
+      - !ruby/object:Gem::Version
+        version: 0.5.1
+  type: :development
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    none: false
+    requirements:
+    - - ~>
+      - !ruby/object:Gem::Version
+        version: 0.5.1
+description: ! "New users to git and Heroku sometimes have trouble\n                         with
+  the syntax of the git commands required to deploy\n                         an application
+  to Heroku. This wrapper combines\n                         the git add, commit,
+  and push commands needed. The\n                         command has no arguments.
+  The user is prompted for a\n                         commit message. The wrapper
+  contains no error handling,\n                         so the user will receive errors
+  from git.\n                         "
+email:
+- pcm@morganthall.com
+executables:
+- gittyup
+extensions: []
+extra_rdoc_files: []
+files:
+- .gitignore
+- Gemfile
+- LICENSE.txt
+- README.md
+- Rakefile
+- bin/gittyup
+- features/adcopu.feature
+- features/readme.md
+- features/step_definitions/adcopu_steps.rb
+- features/support/env.rb
+- gittyup.gemspec
+- lib/gittyup.rb
+- lib/gittyup/version.rb
+homepage: http://github.com/slothbear/gittyup
+licenses: []
+post_install_message: 
+rdoc_options: []
+require_paths:
+- lib
+required_ruby_version: !ruby/object:Gem::Requirement
+  none: false
+  requirements:
+  - - ! '>='
+    - !ruby/object:Gem::Version
+      version: '0'
+required_rubygems_version: !ruby/object:Gem::Requirement
+  none: false
+  requirements:
+  - - ! '>='
+    - !ruby/object:Gem::Version
+      version: '0'
+requirements: []
+rubyforge_project: 
+rubygems_version: 1.8.24
+signing_key: 
+specification_version: 3
+summary: wrapper for git add/commit/push to Heroku
+test_files:
+- features/adcopu.feature
+- features/readme.md
+- features/step_definitions/adcopu_steps.rb
+- features/support/env.rb