stephencelis

# factory_girl for minitest
#
#   Factory.define :user do |f|
#     f.login 'johndoe%d'                          # Sequence.
#     f.email '%{login}@example.com'               # Interpolate.
#     f.password f.password_confirmation('foobar') # Chain.
#   end
#
#   Factory.define :post do |f|
#     f.user { Factory :user }                     # Blocks, if you must.

paulirish

// ==UserScript==
// @name          UTM param stripper
// @author        Paul Irish
// @namespace     http://github.com/paulirish
// @version       1.2
// @description   Drop the UTM params from a URL when the page loads.
// @extra         Cuz you know they're all ugly n shit.
// @include       http*://*
// ==/UserScript==

BPScott

This totally happened, y'all can stop +1ing this now. GitHub Blog post. Direct link to settings where you can set this.

---

#Per-organization / per-repo email overrides - A feature suggestion

Here the concepts "organization" and "user" are interchangeable, I'm talking about an entity that owns a repo, whether it is jQuery or John Resig. I'll stick to using organization as it best represents my original use-case.

##TL;DR

tundal45

Beginner/Intermediate:

• UNIX in a Nutshell
• UNIX Power Tools
• UNIX and Linux System Administration Handbook
• From Bash to Z Shell: Conquering the Command Line
• Working with UNIX Processes

Advanced

jbarnette

class ActiveRecord::Base
  attr_accessible nil

  def update_attributes *args
    raise "Don't call #{self.class.name}#update_attributes. " +
      "Mass assignment is pure evil."
  end
end

justinko

Dear Rubyists,

I just lost a contract because of my code in a Rails project.

The specific code in question is related to a "posting a comment" feature. Here are the details:

In this project, "posting a comment" does not simply entail inserting a row into the database. It involves a procedure to yes, insert a row, but also detect its language, check for spam, send emails, and "share" it to Twitter and Facebook. I believe this algorithm should be encapsulated. I do not believe it belongs in a controller or a model. I do not believe Active Record callbacks should be used.

The "senior developer", whom is the stake holder's right hand man, said this:

xdite

1. Get You a Hug, Every Friday

FridayHug.com http://fridayhug.com

2. Run From a Single File

The Smallest Rails App http://thesmallestrailsapp.com

%w(action_controller/railtie coderay).each &method(:require)

piscisaureus

Locate the section for your github remote in the .git/config file. It looks like this:

[remote "origin"]
	fetch = +refs/heads/*:refs/remotes/origin/*
	url = git@github.com:joyent/node.git

Now add the line fetch = +refs/pull/*/head:refs/remotes/origin/pr/* to this section. Obviously, change the github url to match your project's URL. It ends up looking like this:

josevalim

Sinatra like routes in Rails controllers

A proof of concept of having Sinatra like routes inside your controllers.

How to use

Since the router is gone, feel free to remove config/routes.rb. Then add the file below to lib/action_controller/inline_routes.rb inside your app.

tcrayford

require 'thread'

class Actor
  class ActorDied < RuntimeError; end
  def self.queue
    @queue ||= Queue.new
  end

  def self.push(x)
    queue.push(x)