5j9 5j9

How to reopen a pull-request after a force-push?

Precodinitions

You need the rights to reopen pull requests on the repository.
The pull request hasn't been merged, just closed.

Instructions

Write down the current commit hash of your PR-branch git log --oneline -1 <PR-BRANCH>
Write down the latest commit hash on github before the PR has been closed.
git push -f origin :

How to add more to Git Bash on Windows

Git for Windows comes bundled with the "Git Bash" terminal which is incredibly handy for unix-like commands on a windows machine. It is missing a few standard linux utilities, but it is easy to add ones that have a windows binary available.

The basic idea is that C:\Program Files\Git\mingw64\ is your / directory according to Git Bash (note: depending on how you installed it, the directory might be different. from the start menu, right click on the Git Bash icon and open file location. It might be something like C:\Users\name\AppData\Local\Programs\Git, the mingw64 in this directory is your root. Find it by using pwd -W). If you go to that directory, you will find the typical linux root folder structure (bin, etc, lib and so on).

If you are missing a utility, such as wget, track down a binary for windows and copy the files to the corresponding directories. Sometimes the windows binary have funny prefixes, so

Why I chose Fish over Bash for students

I'm currently the lead instructor at Code Platoon and an instructor/developer at the Turing School of Software and Design.

I've been advocating the Fish shell and when the choice is up to me, I choose that for my students. Enough people ask about the decision, particularly in relation to the preinstalled Bash shell, that I figured it's worth laying out my reasoning.

TL;DR

Python VS ES6 syntax comparison

Python syntax here : 2.7 - online REPL

Javascript ES6 via Babel transpilation - online REPL

Imports

import math

EDIT from 2019: Hi folks. I wrote this gist for myself and some friends, and it seems like it's gotten posted somewhere that's generated some (ahem, heated) discussion. ~~The whitespace was correct when it was posted, and since then GitHub changed how it formats <pre> tags. Look at the raw text if you care about this. I'm sure someone could tell me how to fix it, but~~ (thank you @anzdaddy for suggesting a formatting workaround) honestly this is a random throwaway gist from 2015, and someone more knowledgable about this comparison should just write a proper blog post about it. If you comment here I'll hopefully see it and stick a link to it up here. Cheers. @oconnor663

Here's the canonical TOML example from the TOML README, and a YAML version of the same.

title = "TOML Example"

The Ultimate Git Alias Setup

If you use git on the command-line, you'll eventually find yourself wanting aliases for your most commonly-used commands. It's incredibly useful to be able to explore your repos with only a few keystrokes that eventually get hardcoded into muscle memory.

Some people don't add aliases because they don't want to have to adjust to not having them on a remote server. Personally, I find that having aliases doesn't mean I that forget the underlying commands, and aliases provide such a massive improvement to my workflow that it would be crazy not to have them.

The simplest way to add an alias for a specific git command is to use a standard bash alias.

# .bashrc

	+------------------------------------+---------------+---------------+--------------+-------------------------+
	\| Benchmark \| 3.5-perf.json \| 3.6-perf.json \| Change \| Significance \|
	+====================================+===============+===============+==============+=========================+
	\| 2to3 \| 0.68 \| 0.62 \| 1.09x faster \| Significant (t=65.03) \|
	+------------------------------------+---------------+---------------+--------------+-------------------------+
	\| call_method \| 0.02 \| 0.02 \| 1.07x faster \| Significant (t=46.01) \|
	+------------------------------------+---------------+---------------+--------------+-------------------------+
	\| call_method_slots \| 0.02 \| 0.02 \| 1.06x faster \| Significant (t=29.45) \|
	+------------------------------------+---------------+---------------+--------------+-------------------------+
	\| call_method_un

	[
	{ "code": "aa", "name": "Afar" },
	{ "code": "ab", "name": "Abkhazian" },
	{ "code": "ae", "name": "Avestan" },
	{ "code": "af", "name": "Afrikaans" },
	{ "code": "ak", "name": "Akan" },
	{ "code": "am", "name": "Amharic" },
	{ "code": "an", "name": "Aragonese" },
	{ "code": "ar", "name": "Arabic" },
	{ "code": "as", "name": "Assamese" },

	[diff]
	tool = pycharm
	[difftool "pycharm"]
	cmd = /usr/local/bin/pycharm diff "$LOCAL" "$REMOTE" && echo "Press enter to continue..." && read
	[merge]
	tool = pycharm
	keepBackup = false
	[mergetool "pycharm"]
	cmd = /usr/local/bin/pycharm merge "$LOCAL" "$REMOTE" "$BASE" "$MERGED"