maia

class ActiveRecord::Base

  class << self

    def select_values(*args)
      options = args.extract_options!
      validate_find_options(options)
      set_readonly_option!(options)
      raise "select_values does not support the :include option" if options[:include]

maia

##
#
# This module allows job classes to complete a batch and only then add workers of other classes.
# When including it, call #perform_as_batch(ids) instead of manually calling #perform,
# use batch_key to #perform as second parameter and set it as instance variable, and
# add #run_when_batch_completed with whatever shall happen once the batch is completed.
require 'active_support/concern'
module ChainedJob
  extend ActiveSupport::Concern

maia

Whether you're trying to give back to the open source community or collaborating on your own projects, knowing how to properly fork and generate pull requests is essential. Unfortunately, it's quite easy to make mistakes or not know what you should do when you're initially learning the process. I know that I certainly had considerable initial trouble with it, and I found a lot of the information on GitHub and around the internet to be rather piecemeal and incomplete - part of the process described here, another there, common hangups in a different place, and so on.

In an attempt to coallate this information for myself and others, this short tutorial is what I've found to be fairly standard procedure for creating a fork, doing your work, issuing a pull request, and merging that pull request back into the original project.

Creating a Fork

Just head over to the GitHub page and click the "Fork" button. It's just that simple. Once you've done that, you can use your favorite git client to clone your repo or j