ryanb

Railties 3.1 RC4

• The new rake task assets:clean removes precompiled assets. [fxn]

• Application and plugin generation run bundle install unless --skip-gemfile or --skip-bundle. [fxn]

• Fixed database tasks for jdbc* adapters #jruby [Rashmi Yadav]

• Template generation for jdbcpostgresql #jruby [Vishnu Atrai]

erikh

#!/usr/bin/env sh

##
# This is script with usefull tips taken from:
#   https://github.com/mathiasbynens/dotfiles/blob/master/.osx
#
# install it:
#   curl -sL https://raw.github.com/gist/2108403/hack.sh | sh
#

wycats

JSON API

There are two JSON API styles:

• The ID Style
• The URL Style

The ID style is the easiest to get started with, but requires that your clients be able to guess the URLs for related documents. It also locks your API into a particular URL structure, which may become a problem as your API grows.

The URL style requires less guessing on the client side, and makes clients more resilient to API changes, but is trickier to use with relationships and compound documents.

Bahanix

#!/bin/sh

STASH_NAME="$(git stash list | grep `git branch | grep \* | cut -d ' ' -f2` | head -n1 | cut -d':' -f1)"
if [ -n "$STASH_NAME" ]
then
  echo "Last stash on this branch:"
  git --no-pager stash show "$STASH_NAME" -p
  echo "To keep your stash list clean, consider using one of the followings:"
  echo "git stash pop \"$STASH_NAME\""
  echo "git stash drop \"$STASH_NAME\""

johndevs

# Provide $query as a variable. 
# The query is the same as you would enter into the search field e.g. "org:johndevs in:name feedreader"

query GetFilesQuery($branch: GitObjectID, $query: String!) {
 search(first: 1, type: REPOSITORY, query: $query) {
    edges {
      node {
        ... on Repository {
          object(expression: "master:", oid: $branch) {
            ... on Tree {