got_fixed 0.0.1

data/lib/tasks/got_fixed_tasks.rake

@@ -0,0 +1,56 @@
+# desc "Explaining what the task does"
+# task :got_fixed do
+#   # Task goes here
+# end
+
+namespace :got_fixed do
+
+  desc "Import github issues from repos found in config/got_fixed.yml"
+  task :import_github => :environment do
+    issue_factory = GotFixed::IssueFactory.new
+
+    GotFixed.config[:github].each do |repo|
+      github = GotFixed::Adapters::Github.new
+      issues = github.issues(repo)
+      puts "Found #{issues.size} issues for #{repo_name(repo)}, filtering on labels '#{repo[:labels]}'"
+
+      issues.each do |gh_issue|
+        issue = issue_factory.from_github gh_issue
+        if issue.save
+          puts "Issue ##{gh_issue["number"]} #{issue.persisted? ? "updat" : "import"}ed: #{gh_issue["title"]}"
+        else
+          puts "\e[32mCould not import issue ##{gh_issue["number"]} from #{repo_name(repo)}: #{issue.errors.messages}\e[0;0m"
+        end
+      end
+    end
+  end
+
+  task :register_github_webhook => :environment do
+    listener_url = nil
+    while true
+      puts "What is the base URI of your host app? (e.g. https://myapp.herokuapp.com)"
+      host = STDIN.gets.strip
+
+      listener_url = GotFixed::Engine.routes.url_helpers.github_webhook_issues_url :host => host
+      puts "We'll tell Github to post issue changes to \e[32m#{listener_url}\e[0;0m. Looks good? (y/n)"
+      break if STDIN.gets.strip == "y"
+    end
+
+    GotFixed.config[:github].each do |repo|
+      if repo[:webhook_secret].blank?
+        puts "/!\\ Empty webhook_secret for repository #{repo_name(repo)}, skipping webhook creation"
+        next
+      end
+
+      github = GotFixed::Adapters::Github.new(repo)
+      github.create_hook :url => listener_url, :secret => repo[:webhook_secret]
+      puts "Successfully created hook for #{repo_name(repo)}. " +
+           "You can visualize it at https://github.com/#{repo_name(repo)}/settings/hooks"
+    end
+  end
+
+  def repo_name(repo)
+    "#{repo[:owner]}/#{repo[:repo]}}"
+  end
+
+end

data/spec/controllers/got_fixed/issues_controller_spec.rb

@@ -0,0 +1,194 @@
+require 'spec_helper'
+
+# This spec was generated by rspec-rails when you ran the scaffold generator.
+# It demonstrates how one might use RSpec to specify the controller code that
+# was generated by Rails when you ran the scaffold generator.
+#
+# It assumes that the implementation code is generated by the rails scaffold
+# generator.  If you are using any extension libraries to generate different
+# controller code, this generated spec may or may not pass.
+#
+# It only uses APIs available in rails and/or rspec-rails.  There are a number
+# of tools you can use to make these specs even more expressive, but we're
+# sticking to rails and rspec-rails APIs to keep things simple and stable.
+#
+# Compared to earlier versions of this generator, there is very limited use of
+# stubs and message expectations in this spec.  Stubs are only used when there
+# is no simpler way to get a handle on the object needed for the example.
+# Message expectations are only used when there is no simpler way to specify
+# that an instance is receiving a specific message.
+
+module GotFixed
+  describe IssuesController do
+
+    routes { GotFixed::Engine.routes }
+
+    # This should return the minimal set of attributes required to create a valid
+    # Issue. As you add validations to Issue, be sure to
+    # update the return value of this method accordingly.
+    def valid_attributes
+      { "title" => "MyString" }
+    end
+
+    # This should return the minimal set of values that should be in the session
+    # in order to pass any filters (e.g. authentication) defined in
+    # IssuesController. Be sure to keep this updated too.
+    def valid_session
+      {}
+    end
+
+    describe "GET index" do
+      it "assigns all issues as @issues" do
+        issue = Issue.create! valid_attributes
+        get :index, {}, valid_session
+        assigns(:issues).should eq([issue])
+      end
+    end
+
+    describe "POST github_webhook" do
+      it "creates an issue from an 'closed' event" do
+        params = JSON.load(File.open "spec/factories/github/hook-issues-event.json")
+        request.headers["X-Hub-Signature"] = "sha1=7e5f575e2e92360b4f13a2100d930e770f26fde3"
+        request.headers["Content-Type"] = "application/json"
+        request.env["RAW_POST_DATA"] = JSON.generate(params)  # Hackish as Rspec creates a url-encoded payload...
+        post :github_webhook, params, :format => :json
+
+        @issue = assigns(:issue)
+        @issue.should be_valid
+        @issue.vendor_id.should eq params["issue"]["id"].to_s
+        @issue.title.should eq params["issue"]["title"]
+        @issue.closed.should be_true
+      end
+    end
+
+    describe "POST subscribe" do
+      before(:each) do
+        @issue = FactoryGirl.create :got_fixed_issue
+        @issue.users.should be_blank
+      end
+
+      it "creates a user and subscribe him if the email does not exist" do
+        post :subscribe, :id => @issue.id, :user => { :email => "foo@bar.com" }, :format => :js
+
+        @user = assigns(:user)
+        @user.email.should eq "foo@bar.com"
+        @issue.reload.users.should_not be_blank
+      end
+
+      it "should subscribe an existing user" do
+        User.create! :email => "foo@bar.com"
+        post :subscribe, :id => @issue.id, :user => { :email => "foo@bar.com" }, :format => :js
+
+        @user = assigns(:user)
+        @user.email.should eq "foo@bar.com"
+        @issue.reload.users.should_not be_blank
+      end
+
+      it "should behave well when user already registered (not register him twice)" do
+        @issue.users << User.create!(:email => "foo@bar.com")
+        @issue.save
+
+        post :subscribe, :id => @issue.id, :user => { :email => "foo@bar.com" }, :format => :js
+
+        @issue.reload.users.size.should eq 1
+      end
+    end
+
+    # describe "POST create" do
+    #   describe "with valid params" do
+    #     it "creates a new Issue" do
+    #       expect {
+    #         post :create, {:issue => valid_attributes}, valid_session
+    #       }.to change(Issue, :count).by(1)
+    #     end
+
+    #     it "assigns a newly created issue as @issue" do
+    #       post :create, {:issue => valid_attributes}, valid_session
+    #       assigns(:issue).should be_a(Issue)
+    #       assigns(:issue).should be_persisted
+    #     end
+
+    #     it "redirects to the created issue" do
+    #       post :create, {:issue => valid_attributes}, valid_session
+    #       response.should redirect_to(Issue.last)
+    #     end
+    #   end
+
+    #   describe "with invalid params" do
+    #     it "assigns a newly created but unsaved issue as @issue" do
+    #       # Trigger the behavior that occurs when invalid params are submitted
+    #       Issue.any_instance.stub(:save).and_return(false)
+    #       post :create, {:issue => { "title" => "invalid value" }}, valid_session
+    #       assigns(:issue).should be_a_new(Issue)
+    #     end
+
+    #     it "re-renders the 'new' template" do
+    #       # Trigger the behavior that occurs when invalid params are submitted
+    #       Issue.any_instance.stub(:save).and_return(false)
+    #       post :create, {:issue => { "title" => "invalid value" }}, valid_session
+    #       response.should render_template("new")
+    #     end
+    #   end
+    # end
+
+    # describe "PUT update" do
+    #   describe "with valid params" do
+    #     it "updates the requested issue" do
+    #       issue = Issue.create! valid_attributes
+    #       # Assuming there are no other issues in the database, this
+    #       # specifies that the Issue created on the previous line
+    #       # receives the :update_attributes message with whatever params are
+    #       # submitted in the request.
+    #       Issue.any_instance.should_receive(:update_attributes).with({ "title" => "MyString" })
+    #       put :update, {:id => issue.to_param, :issue => { "title" => "MyString" }}, valid_session
+    #     end
+
+    #     it "assigns the requested issue as @issue" do
+    #       issue = Issue.create! valid_attributes
+    #       put :update, {:id => issue.to_param, :issue => valid_attributes}, valid_session
+    #       assigns(:issue).should eq(issue)
+    #     end
+
+    #     it "redirects to the issue" do
+    #       issue = Issue.create! valid_attributes
+    #       put :update, {:id => issue.to_param, :issue => valid_attributes}, valid_session
+    #       response.should redirect_to(issue)
+    #     end
+    #   end
+
+    #   describe "with invalid params" do
+    #     it "assigns the issue as @issue" do
+    #       issue = Issue.create! valid_attributes
+    #       # Trigger the behavior that occurs when invalid params are submitted
+    #       Issue.any_instance.stub(:save).and_return(false)
+    #       put :update, {:id => issue.to_param, :issue => { "title" => "invalid value" }}, valid_session
+    #       assigns(:issue).should eq(issue)
+    #     end
+
+    #     it "re-renders the 'edit' template" do
+    #       issue = Issue.create! valid_attributes
+    #       # Trigger the behavior that occurs when invalid params are submitted
+    #       Issue.any_instance.stub(:save).and_return(false)
+    #       put :update, {:id => issue.to_param, :issue => { "title" => "invalid value" }}, valid_session
+    #       response.should render_template("edit")
+    #     end
+    #   end
+    # end
+
+    # describe "DELETE destroy" do
+    #   it "destroys the requested issue" do
+    #     issue = Issue.create! valid_attributes
+    #     expect {
+    #       delete :destroy, {:id => issue.to_param}, valid_session
+    #     }.to change(Issue, :count).by(-1)
+    #   end
+
+    #   it "redirects to the issues list" do
+    #     issue = Issue.create! valid_attributes
+    #     delete :destroy, {:id => issue.to_param}, valid_session
+    #     response.should redirect_to(issues_url)
+    #   end
+    # end
+
+  end
+end

data/spec/dummy/README.rdoc

@@ -0,0 +1,261 @@
+== Welcome to Rails
+
+Rails is a web-application framework that includes everything needed to create
+database-backed web applications according to the Model-View-Control pattern.
+
+This pattern splits the view (also called the presentation) into "dumb"
+templates that are primarily responsible for inserting pre-built data in between
+HTML tags. The model contains the "smart" domain objects (such as Account,
+Product, Person, Post) that holds all the business logic and knows how to
+persist themselves to a database. The controller handles the incoming requests
+(such as Save New Account, Update Product, Show Post) by manipulating the model
+and directing data to the view.
+
+In Rails, the model is handled by what's called an object-relational mapping
+layer entitled Active Record. This layer allows you to present the data from
+database rows as objects and embellish these data objects with business logic
+methods. You can read more about Active Record in
+link:files/vendor/rails/activerecord/README.html.
+
+The controller and view are handled by the Action Pack, which handles both
+layers by its two parts: Action View and Action Controller. These two layers
+are bundled in a single package due to their heavy interdependence. This is
+unlike the relationship between the Active Record and Action Pack that is much
+more separate. Each of these packages can be used independently outside of
+Rails. You can read more about Action Pack in
+link:files/vendor/rails/actionpack/README.html.
+
+
+== Getting Started
+
+1. At the command prompt, create a new Rails application:
+       <tt>rails new myapp</tt> (where <tt>myapp</tt> is the application name)
+
+2. Change directory to <tt>myapp</tt> and start the web server:
+       <tt>cd myapp; rails server</tt> (run with --help for options)
+
+3. Go to http://localhost:3000/ and you'll see:
+       "Welcome aboard: You're riding Ruby on Rails!"
+
+4. Follow the guidelines to start developing your application. You can find
+the following resources handy:
+
+* The Getting Started Guide: http://guides.rubyonrails.org/getting_started.html
+* Ruby on Rails Tutorial Book: http://www.railstutorial.org/
+
+
+== Debugging Rails
+
+Sometimes your application goes wrong. Fortunately there are a lot of tools that
+will help you debug it and get it back on the rails.
+
+First area to check is the application log files. Have "tail -f" commands
+running on the server.log and development.log. Rails will automatically display
+debugging and runtime information to these files. Debugging info will also be
+shown in the browser on requests from 127.0.0.1.
+
+You can also log your own messages directly into the log file from your code
+using the Ruby logger class from inside your controllers. Example:
+
+  class WeblogController < ActionController::Base
+    def destroy
+      @weblog = Weblog.find(params[:id])
+      @weblog.destroy
+      logger.info("#{Time.now} Destroyed Weblog ID ##{@weblog.id}!")
+    end
+  end
+
+The result will be a message in your log file along the lines of:
+
+  Mon Oct 08 14:22:29 +1000 2007 Destroyed Weblog ID #1!
+
+More information on how to use the logger is at http://www.ruby-doc.org/core/
+
+Also, Ruby documentation can be found at http://www.ruby-lang.org/. There are
+several books available online as well:
+
+* Programming Ruby: http://www.ruby-doc.org/docs/ProgrammingRuby/ (Pickaxe)
+* Learn to Program: http://pine.fm/LearnToProgram/ (a beginners guide)
+
+These two books will bring you up to speed on the Ruby language and also on
+programming in general.
+
+
+== Debugger
+
+Debugger support is available through the debugger command when you start your
+Mongrel or WEBrick server with --debugger. This means that you can break out of
+execution at any point in the code, investigate and change the model, and then,
+resume execution! You need to install ruby-debug to run the server in debugging
+mode. With gems, use <tt>sudo gem install ruby-debug</tt>. Example:
+
+  class WeblogController < ActionController::Base
+    def index
+      @posts = Post.all
+      debugger
+    end
+  end
+
+So the controller will accept the action, run the first line, then present you
+with a IRB prompt in the server window. Here you can do things like:
+
+  >> @posts.inspect
+  => "[#<Post:0x14a6be8
+          @attributes={"title"=>nil, "body"=>nil, "id"=>"1"}>,
+       #<Post:0x14a6620
+          @attributes={"title"=>"Rails", "body"=>"Only ten..", "id"=>"2"}>]"
+  >> @posts.first.title = "hello from a debugger"
+  => "hello from a debugger"
+
+...and even better, you can examine how your runtime objects actually work:
+
+  >> f = @posts.first
+  => #<Post:0x13630c4 @attributes={"title"=>nil, "body"=>nil, "id"=>"1"}>
+  >> f.
+  Display all 152 possibilities? (y or n)
+
+Finally, when you're ready to resume execution, you can enter "cont".
+
+
+== Console
+
+The console is a Ruby shell, which allows you to interact with your
+application's domain model. Here you'll have all parts of the application
+configured, just like it is when the application is running. You can inspect
+domain models, change values, and save to the database. Starting the script
+without arguments will launch it in the development environment.
+
+To start the console, run <tt>rails console</tt> from the application
+directory.
+
+Options:
+
+* Passing the <tt>-s, --sandbox</tt> argument will rollback any modifications
+  made to the database.
+* Passing an environment name as an argument will load the corresponding
+  environment. Example: <tt>rails console production</tt>.
+
+To reload your controllers and models after launching the console run
+<tt>reload!</tt>
+
+More information about irb can be found at:
+link:http://www.rubycentral.org/pickaxe/irb.html
+
+
+== dbconsole
+
+You can go to the command line of your database directly through <tt>rails
+dbconsole</tt>. You would be connected to the database with the credentials
+defined in database.yml. Starting the script without arguments will connect you
+to the development database. Passing an argument will connect you to a different
+database, like <tt>rails dbconsole production</tt>. Currently works for MySQL,
+PostgreSQL and SQLite 3.
+
+== Description of Contents
+
+The default directory structure of a generated Ruby on Rails application:
+
+  |-- app
+  |   |-- assets
+  |   |   |-- images
+  |   |   |-- javascripts
+  |   |   `-- stylesheets
+  |   |-- controllers
+  |   |-- helpers
+  |   |-- mailers
+  |   |-- models
+  |   `-- views
+  |       `-- layouts
+  |-- config
+  |   |-- environments
+  |   |-- initializers
+  |   `-- locales
+  |-- db
+  |-- doc
+  |-- lib
+  |   |-- assets
+  |   `-- tasks
+  |-- log
+  |-- public
+  |-- script
+  |-- test
+  |   |-- fixtures
+  |   |-- functional
+  |   |-- integration
+  |   |-- performance
+  |   `-- unit
+  |-- tmp
+  |   `-- cache
+  |       `-- assets
+  `-- vendor
+      |-- assets
+      |   |-- javascripts
+      |   `-- stylesheets
+      `-- plugins
+
+app
+  Holds all the code that's specific to this particular application.
+
+app/assets
+  Contains subdirectories for images, stylesheets, and JavaScript files.
+
+app/controllers
+  Holds controllers that should be named like weblogs_controller.rb for
+  automated URL mapping. All controllers should descend from
+  ApplicationController which itself descends from ActionController::Base.
+
+app/models
+  Holds models that should be named like post.rb. Models descend from
+  ActiveRecord::Base by default.
+
+app/views
+  Holds the template files for the view that should be named like
+  weblogs/index.html.erb for the WeblogsController#index action. All views use
+  eRuby syntax by default.
+
+app/views/layouts
+  Holds the template files for layouts to be used with views. This models the
+  common header/footer method of wrapping views. In your views, define a layout
+  using the <tt>layout :default</tt> and create a file named default.html.erb.
+  Inside default.html.erb, call <% yield %> to render the view using this
+  layout.
+
+app/helpers
+  Holds view helpers that should be named like weblogs_helper.rb. These are
+  generated for you automatically when using generators for controllers.
+  Helpers can be used to wrap functionality for your views into methods.
+
+config
+  Configuration files for the Rails environment, the routing map, the database,
+  and other dependencies.
+
+db
+  Contains the database schema in schema.rb. db/migrate contains all the
+  sequence of Migrations for your schema.
+
+doc
+  This directory is where your application documentation will be stored when
+  generated using <tt>rake doc:app</tt>
+
+lib
+  Application specific libraries. Basically, any kind of custom code that
+  doesn't belong under controllers, models, or helpers. This directory is in
+  the load path.
+
+public
+  The directory available for the web server. Also contains the dispatchers and the
+  default HTML files. This should be set as the DOCUMENT_ROOT of your web
+  server.
+
+script
+  Helper scripts for automation and generation.
+
+test
+  Unit and functional tests along with fixtures. When using the rails generate
+  command, template test files will be generated for you and placed in this
+  directory.
+
+vendor
+  External libraries that the application depends on. Also includes the plugins
+  subdirectory. If the app has frozen rails, those gems also go here, under
+  vendor/rails/. This directory is in the load path.

data/spec/dummy/Rakefile

@@ -0,0 +1,7 @@
+#!/usr/bin/env rake
+# Add your own tasks in files placed in lib/tasks ending in .rake,
+# for example lib/tasks/capistrano.rake, and they will automatically be available to Rake.
+
+require File.expand_path('../config/application', __FILE__)
+
+Dummy::Application.load_tasks

data/spec/dummy/app/assets/javascripts/application.js

@@ -0,0 +1,15 @@
+// This is a manifest file that'll be compiled into application.js, which will include all the files
+// listed below.
+//
+// Any JavaScript/Coffee file within this directory, lib/assets/javascripts, vendor/assets/javascripts,
+// or vendor/assets/javascripts of plugins, if any, can be referenced here using a relative path.
+//
+// It's not advisable to add code directly here, but if you do, it'll appear at the bottom of the
+// the compiled file.
+//
+// WARNING: THE FIRST BLANK LINE MARKS THE END OF WHAT'S TO BE PROCESSED, ANY BLANK LINE SHOULD
+// GO AFTER THE REQUIRES BELOW.
+//
+//= require jquery
+//= require jquery_ujs
+//= require_tree .

data/spec/dummy/app/assets/stylesheets/application.css

@@ -0,0 +1,13 @@
+/*
+ * This is a manifest file that'll be compiled into application.css, which will include all the files
+ * listed below.
+ *
+ * Any CSS and SCSS file within this directory, lib/assets/stylesheets, vendor/assets/stylesheets,
+ * or vendor/assets/stylesheets of plugins, if any, can be referenced here using a relative path.
+ *
+ * You're free to add application-wide styles to this file and they'll appear at the top of the
+ * compiled file, but it's generally better to create a new file per style scope.
+ *
+ *= require_self
+ *= require_tree .
+ */

data/spec/dummy/app/controllers/application_controller.rb

@@ -0,0 +1,3 @@
+class ApplicationController < ActionController::Base
+  protect_from_forgery
+end

data/spec/dummy/app/helpers/application_helper.rb

@@ -0,0 +1,2 @@
+module ApplicationHelper
+end

data/spec/dummy/app/views/layouts/application.html.erb

@@ -0,0 +1,14 @@
+<!DOCTYPE html>
+<html>
+<head>
+  <title>Dummy</title>
+  <%= stylesheet_link_tag    "application", :media => "all" %>
+  <%= javascript_include_tag "application" %>
+  <%= csrf_meta_tags %>
+</head>
+<body>
+
+<%= yield %>
+
+</body>
+</html>

data/spec/dummy/config/application.rb

@@ -0,0 +1,65 @@
+require File.expand_path('../boot', __FILE__)
+
+# Pick the frameworks you want:
+require "active_record/railtie"
+require "action_controller/railtie"
+require "action_mailer/railtie"
+# require "active_resource/railtie"
+require "sprockets/railtie"
+# require "rails/test_unit/railtie"
+
+Bundler.require(*Rails.groups)
+require "got_fixed"
+
+module Dummy
+  class Application < Rails::Application
+    # Settings in config/environments/* take precedence over those specified here.
+    # Application configuration should go into files in config/initializers
+    # -- all .rb files in that directory are automatically loaded.
+
+    # Custom directories with classes and modules you want to be autoloadable.
+    # config.autoload_paths += %W(#{config.root}/extras)
+
+    # Only load the plugins named here, in the order given (default is alphabetical).
+    # :all can be used as a placeholder for all plugins not explicitly named.
+    # config.plugins = [ :exception_notification, :ssl_requirement, :all ]
+
+    # Activate observers that should always be running.
+    # config.active_record.observers = :cacher, :garbage_collector, :forum_observer
+
+    # Set Time.zone default to the specified zone and make Active Record auto-convert to this zone.
+    # Run "rake -D time" for a list of tasks for finding time zone names. Default is UTC.
+    # config.time_zone = 'Central Time (US & Canada)'
+
+    # The default locale is :en and all translations from config/locales/*.rb,yml are auto loaded.
+    # config.i18n.load_path += Dir[Rails.root.join('my', 'locales', '*.{rb,yml}').to_s]
+    # config.i18n.default_locale = :de
+
+    # Configure the default encoding used in templates for Ruby 1.9.
+    config.encoding = "utf-8"
+
+    # Configure sensitive parameters which will be filtered from the log file.
+    config.filter_parameters += [:password]
+
+    # Enable escaping HTML in JSON.
+    config.active_support.escape_html_entities_in_json = true
+
+    # Use SQL instead of Active Record's schema dumper when creating the database.
+    # This is necessary if your schema can't be completely dumped by the schema dumper,
+    # like if you have constraints or database-specific column types
+    # config.active_record.schema_format = :sql
+
+    # Enforce whitelist mode for mass assignment.
+    # This will create an empty whitelist of attributes available for mass-assignment for all models
+    # in your app. As such, your models will need to explicitly whitelist or blacklist accessible
+    # parameters by using an attr_accessible or attr_protected declaration.
+    # config.active_record.whitelist_attributes = true
+
+    # Enable the asset pipeline
+    config.assets.enabled = true
+
+    # Version of your assets, change this if you want to expire all your assets
+    config.assets.version = '1.0'
+  end
+end
+

data/spec/dummy/config/boot.rb

@@ -0,0 +1,10 @@
+require 'rubygems'
+gemfile = File.expand_path('../../../../Gemfile', __FILE__)
+
+if File.exist?(gemfile)
+  ENV['BUNDLE_GEMFILE'] = gemfile
+  require 'bundler'
+  Bundler.setup
+end
+
+$:.unshift File.expand_path('../../../../lib', __FILE__)

data/spec/dummy/config/database.yml

@@ -0,0 +1,25 @@
+# SQLite version 3.x
+#   gem install sqlite3
+#
+#   Ensure the SQLite 3 gem is defined in your Gemfile
+#   gem 'sqlite3'
+development:
+  adapter: sqlite3
+  database: db/development.sqlite3
+  pool: 5
+  timeout: 5000
+
+# Warning: The database defined as "test" will be erased and
+# re-generated from your development database when you run "rake".
+# Do not set this db to the same as development or production.
+test:
+  adapter: sqlite3
+  database: db/test.sqlite3
+  pool: 5
+  timeout: 5000
+
+production:
+  adapter: sqlite3
+  database: db/production.sqlite3
+  pool: 5
+  timeout: 5000

data/spec/dummy/config/environment.rb

@@ -0,0 +1,5 @@
+# Load the rails application
+require File.expand_path('../application', __FILE__)
+
+# Initialize the rails application
+Dummy::Application.initialize!