gorenje

rvm use --create ruby-1.9.2-p180@grcode

gorenje

For this to work, i use a commit hook that automagically includes a ref #... in all commits on 
a feature branch ===> https://gist.github.com/1012062

This also assumes that you have a remote called 'wooga' that is the master of your fork. The owner 
of the master repository is also assumed to be 'wooga'.

prompt(master)> git-fetch-all ## see https://gist.github.com/1012002
prompt(master)> git merge wooga/master ## update local master
prompt(master)> git push ## update origin, i.e. my fork

gorenje

class String
  def remove_indent
    self =~ /\A([ \t]+)/ ? gsub(/\n#{$1}/, "\n").strip : self
  end
end

module Hub
  module Commands
    def feature_branch(args)
      user_arg, issue_num, postfix = nil, nil, nil

gorenje

#!/usr/bin/env ruby
#
# This file, hub, is generated code.
# Please DO NOT EDIT or send patches for it.
#
# Please take a look at the source from
# https://github.com/defunkt/hub
# and submit patches against the individual files
# that build hub.
#

gorenje

source :rubygems

gem 'sinatra'
gem 'json'
gem 'omniauth'
gem 'omniauth-oauth2'
gem 'omniauth-github'
gem 'omniauth-facebook'
gem 'omniauth-twitter'
# gem 'omniauth-att', :path => File.expand_path("./../../omniauth-att", __FILE__)

gorenje

Introduction

This post attempts to provide Subversion developers a new perspective on Git and how git is differs from
subversion but not using the usual “git is distributed development” or “git is peer-to-peer versioning
management”, which tend not provide an argument for an existing subversion project to switch to git.

Instead, I will attempt to provide a historical background to the development of the first versioning
tools and how these lead to the development of git. It is more that probably that certain historical events
mentioned here are completely and utterly wrong, this not intended. Corrections and improvements are very
welcome!

gorenje

require 'zendesk_api'

# retrieve login details from yml file.
z = get_login_details(:zendesk)
client = ZendeskAPI::Client.new do |config|
  config.url = "https://#{z.first}.zendesk.com/api/v2"
  config.username = z[1]
  config.password = z.last

  require 'logger'

gorenje

#!/usr/bin/ruby
#
# Author: Gerrit Riessen, [email protected]
# Copyright (C) 2009 Gerrit Riessen
# This code is licensed under the GNU Public License.
#
# $Id$

require 'rubygems'
require 'fileutils'

gorenje

Scenario:

Private repo which references a private gem can't be built because the gem can't be checked out. The gem in question is installed via bundler and a Gemfile.

Question:

I saw in the output of the test that TravisCI creates a id_rsa key:

gorenje

// -*- c -*-

#define TO_INT(arg1,arg2,arg3,arg4,arg5,arg6,arg7,arg8,arg9) \
  (256*arg1) + (128*arg2) + (64*arg3) + (32*arg4) + (16*arg5) + \
  (  8*arg6) + (  4*arg7) + ( 2*arg8) + ( 1*arg9)

const int lookup[] = { 1, 2, 4, 8, 16, 32, 64, 128, 256 };

const int SwitchPin = 13;
const int SwitchPin2 = 12;