MichaelCurrin

Get Pull Requests using GH's GraphQL API

How to get Pull Requests data using Github in the browser, or using the API to allow for automating reporting or building in values into a website.

Resources

• GitHub GQL API: https://developer.github.com/v4/
• Explorer: https://developer.github.com/v4/explorer/
• Github community topics - these were used to understand the syntax needed.

swalkinshaw

Moved to Shopify/graphql-design-tutorial

mileszs

How to Hire Developers

1. Go to the events the type of developers you want to hire go to. Do this even when you aren't actively hiring.
2. Try to sponsor or otherwise support the events/groups/newsletters/things the type of developers you want to hire like. Do this even when you aren't actually hiring.
3. Favor smart people who fit your culture over resumés that check your requirements boxes.
4. If you can't find enough examples of work to suffice, and must do a technical assessment, try to fashion a low-pressure one. Example: Make an empty private GitHub repo. Give them a task / thing to build and have them make it a pull request to that repo. If you aren't going to bring them in for an actual interview after they submit their homework, at least provide feedback on the pull request. If you are going to bring them in, chat with them about their homework, including talking casually about things they might do differently, or things they might add.

Why should you do 1 and 2 when you aren't hiring? You might

ryanflorence

var pureRender = (Component) => {
  Object.assign(Component.prototype, {
    shouldComponentUpdate (nextProps, nextState) {
      return !shallowEqual(this.props, nextProps) ||
             !shallowEqual(this.state, nextState);
    }
  });
};

module.exports = pureRender;

scott-joe

###Create and checkout a new branch git checkout -b [branchName]

###Checkout a remote branch git checkout -b [localBranchName] origin/[remoteBranchName]

###Push local branch to remote git push -u origin [branchName]

###Delete remote branch

jkubacki

#!/usr/bin/env sh

# checks to see if running 
launchctl list | grep elasticsearch
 
launchctl unload ~/Library/LaunchAgents/homebrew.mxcl.elasticsearch.plist
launchctl remove homebrew.mxcl.elasticsearch

pkill -f elasticsearch

bendc

// array utils
// =================================================================================================

const combine = (...arrays) => [].concat(...arrays);

const compact = arr => arr.filter(Boolean);

const contains = (() => Array.prototype.includes
  ? (arr, value) => arr.includes(value)
  : (arr, value) => arr.some(el => el === value)

DanHerbert

OBSOLETE

This entire guide is based on an old version of Homebrew/Node and no longer applies. It was only ever intended to fix a specific error message which has since been fixed. I've kept it here for historical purposes, but it should no longer be used. Homebrew maintainers have fixed things and the options mentioned don't exist and won't work.

I still believe it is better to manually install npm separately since having a generic package manager maintain another package manager is a bad idea, but the instructions below don't explain how to do that.

Fixing npm On Mac OS X for Homebrew Users

Installing node through Homebrew can cause problems with npm for globally installed packages. To fix it quickly, use the solution below. An explanation is also included at the end of this document.