timm-oh

# app/models/application_record.rb

class ApplicationRecord < ActiveRecord::Base
  # Didn't change #update_column because it uses #update_columns under the hood.
  def update_columns(attrs)
    new_attrs = attrs.symbolize_keys
    new_attrs[:updated_at] ||= Time.current if self.class.column_names.include?('updated_at')
    super(new_attrs)
  end

gre

// more minimal version of https://github.com/olahol/scrollparent.js/blob/master/scrollparent.js
const regex = /(auto|scroll)/;

const style = (node, prop) =>
  getComputedStyle(node, null).getPropertyValue(prop);

const scroll = (node) =>
  regex.test(
    style(node, "overflow") +
    style(node, "overflow-y") +

robertpainsi

How to reopen a pull-request after a force-push?

Precodinitions

• You need the rights to reopen pull requests on the repository.
• The pull request hasn't been merged, just closed.

Instructions

1. Write down the current commit hash of your PR-branch git log --oneline -1 <PR-BRANCH>
2. Write down the latest commit hash on github before the PR has been closed.
3. git push -f origin :

nickmccurdy

:uri: http://example.com/?host=<%= hostname %>

brianr

-- select all deploys
select * from deploy;


-- select main columns for all deploys of a specific revision
select id, timestamp,  environment, comment from deploy
where revision = 'some git sha here'


-- deploys of 'production' by revision, and when they were first and last deployed

chsh

#
# A:
# pubsub = PgPubSub.new('channelname')
# pubsub.subscribe do |data|
#  puts "data: #{data} is coming!"
# end
#
# B:
# pubsub = PgPubSub.new('channelname')
# pubsub.publish("hello world")

subfuzion

There are certain files created by particular editors, IDEs, operating systems, etc., that do not belong in a repository. But adding system-specific files to the repo's .gitignore is considered a poor practice. This file should only exclude files and directories that are a part of the package that should not be versioned (such as the node_modules directory) as well as files that are generated (and regenerated) as artifacts of a build process.

All other files should be in your own global gitignore file:

• Create a file called .gitignore in your home directory and add any filepath patterns you want to ignore.
• Tell git where your global gitignore file is.

Note: The specific name and path you choose aren't important as long as you configure git to find it, as shown below. You could substitute .config/git/ignore for .gitignore in your home directory, if you prefer.

defunkt

# Video: http://rubyhoedown2008.confreaks.com/08-chris-wanstrath-keynote.html

Hi everyone, I'm Chris Wanstrath.

When Jeremy asked me to come talk, I said yes.  Hell yes.  Immediately.  But
then I took a few moments and thought, Wait, why?  Why me?  What am I supposed
to say that's interesting?  Something about Ruby, perhaps.  Maybe the
future of it.  The future of something, at least.  That sounds
keynote-y.