randell

SELECT
  l.name AS "Folder Name",
  c.quantity AS "Quantity",
  0 AS "Trade Quantity",
  dn.name AS "Card Name",
  UPPER(de.tl_abb) AS "Set Code",
  de.name AS "Set Name",
  dc."number" AS "Card Number",
  'NearMint' AS "Condition",
  CASE dc.foil

randell

// Enable branch-switching the database.
if (file_exists('../.git/HEAD')) {
  $head_file   = file('../.git/HEAD', FILE_USE_INCLUDE_PATH);
  $head_line   = $head_file[0];
  $head_bits   = explode("/", $head_line, 3);
  $branch_name = trim($head_bits[2]);

  if ($branch_name !== 'master') {
    $branch_name = str_replace('/', '__', $branch_name);
    $branch_name = str_replace('-', '_', $branch_name);

randell

              {% if node.field_hero_image.entity %}
                <img src="{{ file_url(node.field_hero_image.entity.uri.value) }}"
                     alt="{{ node.field_hero_image.alt  }}"
                     {% if node.field_hero_image.title %}
                       title="{{ node.field_hero_image.title }}"
                     {% endif %}
                />
                {% endif %}

randell

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, when I started going through the process of forking and issuing pull requests, I had some trouble figuring out the proper method for doing so and made quite a few mistakes along the way. 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

randell

!*.dat, !*.f4v, !*.gif, !*.jpg, !*.m4a, !*.mp3, !*.pdf, !*.png, !*.tif, !*.zip, !*.tiff

randell

git rm --cached .project
git rm --cached .classpath
git rm --cached -r .settings

randell

# Note: ~/.ssh/environment should not be used, as it
#       already has a different purpose in SSH.

env=~/.ssh/agent.env

# Note: Don't bother checking SSH_AGENT_PID. It's not used
#       by SSH itself, and it might even be incorrect
#       (for example, when using agent-forwarding over SSH).

agent_is_running() {

randell

AuthType Basic
AuthName "Please Log In"
AuthUserFile /some/path/.htpasswd
Require valid-user
Order deny,allow
Deny from all
Allow from 127.0.0.1
Satisfy any

randell

<?php   
// Source http://goo.gl/608FiA
function include_string($file){
    ob_start();
    include $file;
    return ob_get_clean();
}
$content = return_output('some/file.php');

randell

<?php
/*
 * dl-file.php
 *
 * Protect uploaded files with login.
 * 
 * @link http://wordpress.stackexchange.com/questions/37144/protect-wordpress-uploads-if-user-is-not-logged-in
 * 
 * @author hakre <http://hakre.wordpress.com/>
 * @license GPL-3.0+