Add remote2
as a remote
$ git remote -v
remote2 [email protected]:repo2.git (fetch)
remote2 [email protected]:repo2.git (push)
origin [email protected]:repo.git (fetch)
origin [email protected]:repo.git (push)
Add remote2
as a remote
$ git remote -v
remote2 [email protected]:repo2.git (fetch)
remote2 [email protected]:repo2.git (push)
origin [email protected]:repo.git (fetch)
origin [email protected]:repo.git (push)
#!/bin/bash | |
# A simple script to backup an organization's GitHub repositories. | |
#------------------------------------------------------------------------------- | |
# NOTES: | |
#------------------------------------------------------------------------------- | |
# * User @jimklimov (and probably some others called out in the long comment | |
# thread below) have modified this script to make it more robust and keep | |
# up with various changes in the GitHub API and response format at: | |
# https://github.com/jimklimov/github-scripts |
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 = [email protected]: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:
function __git_dirty { | |
git diff --quiet HEAD &>/dev/null | |
[ $? == 1 ] && echo " ↺ " | |
} | |
function __git_branch { | |
__git_ps1 "%s" | |
} | |
function __my_rvm_ruby_version { |
# | |
# Domain Validator by Frank Rietta | |
# (C) 2012 Rietta Inc. All Rights Reserved. | |
# Licensed under terms of the BSD License. | |
# | |
# To use in a validation, add something like this to your model: | |
# | |
# validates :name, :domain => true | |
# | |
class DomainValidator < ActiveModel::EachValidator |
$VERBOSE = nil | |
require File.expand_path('../rooby', __FILE__) | |
Person = Rooby::Class.new 'Person' do | |
define :initialize do |name| | |
@name = name | |
end | |
define :name do |
# -*- coding: utf-8 -*- | |
$:.unshift("/Library/RubyMotion/lib") | |
require 'motion/project' | |
Motion::Project::App.setup do |app| | |
# Use `rake config' to see complete project settings. | |
app.name = 'HelloMailCore' | |
# Configure MailCore | |
app.vendor_project("vendor/MailCore", :xcode, :headers_dir => "{../include,libetpan/build-mac/.build/include/libetpan}", :target => "MailCore iOS") |
I'm Jesse, one of the co-founders of Dev Bootcamp, and the acting curricular editor-in-chief. We get lots of questions about how Dev Bootcamp approaches teaching, what our curriculum is like, and how it differs from other schools and competitors. I thought I'd share some of that with you, starting with a brief overview of our theory of learning and then sharing our introduction to ActiveRecord.
This will be light on theory and heavy on ActiveRecord, so if you're not familiar with SQL or Ruby it might be hard to follow. Mea culpa.
At Dev Bootcamp, we believe that "modeling" is central to learning. The most effective students have a clear model of how the world works and are able to quickly integrate new information int
// setting auth data retrieved from Ti.Facebook login | |
authData = { | |
"facebook" : { | |
"id" : Ti.Facebook.uid, | |
"access_token" : Ti.Facebook.accessToken, | |
"expiration_date" : expDate, // "format: yyyy-MM-dd'T'HH:mm:ss.SSS'Z'" | |
} | |
}; | |
// Either way I resolved the problem, calling _handleSaveResult(true) on the returned user object, |