addyosmani

{
    "name": "my-app",
    "version": "1.0.0",
    "description": "My test app",
    "main": "src/js/index.js",
    "scripts": {
        "jshint:dist": "jshint src/js/*.js",
        "jshint": "npm run jshint:dist",
        "jscs": "jscs src/*.js",
        "browserify": "browserify -s Validating -o ./dist/js/build.js ./lib/index.js",

johnpolacek

[alias]
        recent = "!git for-each-ref --sort=-committerdate refs/heads/ --format='%(committerdate:short) %(refname:short)' | head -n 10"
	co = checkout
	cob = checkout -b
	coo = !git fetch && git checkout
	br = branch
	brd = branch -d
	brD = branch -D
	merged = branch --merged
	st = status

othiym23

#!/bin/sh

set -e
set -x

for package in $(npm -g outdated --parseable --depth=0 | cut -d: -f3)
do
    npm -g install "$package"
done

rliverman

<?php
/**
 * Adding a custom filter
 * A simple copy and paste of the existing Category filter
 * Find this new filter in: WP Admin > Events > Settings > Filterbar
 * Docs for TribeEventsFilter: http://docs.tri.be/Filter-Bar/class-TribeEventsFilter.html
 */
class TribeEventsFilter_CustomClubs extends TribeEventsFilter {
  public $type = 'select';

yellowberri-snippets

<?php
$template = get_page_template();
$template = explode('/', $template);
$template = end($template);
?>

yellowberri-snippets

<?php

$listedInfo = array(
	'client'   => 'Client',
	'city'     => 'Location',
	'date'     => 'Project Date',
	'cost'     => 'Construction Cost',
	'size'     => 'Building Size',
	'schedule' => 'Construction Schedule'
	);

emaildano

<?php
// get the count on the repeater field
// mabye use get_sub_field() instead of get_field() if it's nested
$count = count( get_sub_field( 'the_field' ) );

// begin $count conditions
if ( $count > 1 ) { ?>
  // greater than 1
  <?php the_field( 'great_than_1' ); ?>
<?php } else { ?>

Chaser324

Whether you're trying to give back to the open source community or collaborating on your own projects, knowing how to properly fork and generate pull requests is essential. Unfortunately, it's quite easy to make mistakes or not know what you should do when you're initially learning the process. I know that I certainly had considerable initial trouble with it, and I found a lot of the information on GitHub and around the internet to be rather piecemeal and incomplete - part of the process described here, another there, common hangups in a different place, and so on.

In an attempt to coallate this information for myself and others, this short tutorial is what I've found to be fairly standard procedure for creating a fork, doing your work, issuing a pull request, and merging that pull request back into the original project.

Creating a Fork

Just head over to the GitHub page and click the "Fork" button. It's just that simple. Once you've done that, you can use your favorite git client to clone your repo or j

natelandau

#  ---------------------------------------------------------------------------
#
#  Description:  This file holds all my BASH configurations and aliases
#
#  Sections:
#  1.   Environment Configuration
#  2.   Make Terminal Better (remapping defaults and adding functionality)
#  3.   File and Folder Management
#  4.   Searching
#  5.   Process Management

galengidman

<?php

// first, get the image ID returned by ACF
$image_id = get_field('my_image_field');

// and the image size you want to return
$image_size = 'thumbnail';

// use wp_get_attachment_image_src to return an array containing the image
// we'll pass in the $image_id in the first parameter