Andreas Hochsteger ahochsteger

Get Git log in JSON format

git log --pretty=format:'{%n  "commit": "%H",%n  "abbreviated_commit": "%h",%n  "tree": "%T",%n  "abbreviated_tree": "%t",%n  "parent": "%P",%n  "abbreviated_parent": "%p",%n  "refs": "%D",%n  "encoding": "%e",%n  "subject": "%s",%n  "sanitized_subject_line": "%f",%n  "body": "%b",%n  "commit_notes": "%N",%n  "verification_flag": "%G?",%n  "signer": "%GS",%n  "signer_key": "%GK",%n  "author": {%n    "name": "%aN",%n    "email": "%aE",%n    "date": "%aD"%n  },%n  "commiter": {%n    "name": "%cN",%n    "email": "%cE",%n    "date": "%cD"%n  }%n},'

The only information that aren't fetched are:

%B: raw body (unwrapped subject and body)
%GG: raw verification message from GPG for a signed commit

Jenkins, Protractor and Headless Chrome Browser Setup on Ubuntu 14.04

Update Ubuntu

sudo apt-get update
sudo apt-get upgrade

Install Java

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

	#!/bin/bash
	# btrfs-undelete
	# Copyright (C) 2013 Jörg Walter <[email protected]>
	# This program is free software; you can redistribute it and/or modify it under
	# the term of the GNU General Public License as published by the Free Software
	# Foundation; either version 2 of the License, or any later version.

	if [ ! -b "$1" -o -z "$2" -o -z "$3" ]; then
	echo "Usage: $0 <dev> <file/dir> <dest>" 1>&2
	echo

	'use strict';

	var crypto = require('crypto');
	var debug = require('debug')('withings');
	var request = require('request');
	var _ = require('lodash');

	var EMAIL = process.env.EMAIL;
	var PASSWORD = process.env.PASSWORD;

	#!/bin/bash

	USERNAME=<username>
	PASSWORD=<password>
	INSTANCE="<company>.atlassian.net"
	LOCATION="./Backups/"

	mkdir "Backups"

	# Grabs cookies and generates the backup on the UI.

	#!/usr/bin/env python
	'''Get mercurial hook and post commit message with link to hg page to youtrack issue as comment.

	Installation:
	Add hook entry in your hgrc:
	[hooks]
	incoming = python:/<path>/commit-to-youtrack.py:hook
	[youtrack-hook]
	ID = EXPL,EG,OPS
	AGGRO = False

	[Unit]
	Description=Play2 Server for <site>
	After=network.target

	[Service]
	Type=simple
	PIDFile=<path>/RUNNING_PID

	ExecStartPre=/bin/sh -c 'cd <path> ;/bin/rm RUNNING_PID ; sbt clean compile stage'
	ExecStart=<path>/target/start

	A comparison of Collection+JSON, HAL, JSON-LD and SIREN media types.

	Discussion at

	http://sookocheff.com/posts/2014-03-11-on-choosing-a-hypermedia-format/

	#!/bin/sh
	### BEGIN INIT INFO
	# Provides: playframework
	# Required-Start: $local_fs $remote_fs $network $syslog
	# Required-Stop: $local_fs $remote_fs $network $syslog
	# Default-Start: 2 3 4 5
	# Default-Stop: 0 1 6
	# Short-Description: Start/Stop playframework
	### END INIT INFO
	#