Somu Bhargava Bhargavasomu

There are many Git workflows out there, I heavily suggest also reading the atlassian.com [Git Workflow][article] article as there is more detail then presented here.

The two prevailing workflows are [Gitflow][gitflow] and [feature branches][feature]. IMHO, being more of a subscriber to continuous integration, I feel that the feature branch workflow is better suited.

When using Bash in the command line, it leaves a bit to be desired when it comes to awareness of state. I would suggest following these instructions on [setting up GIT Bash autocompletion][git-auto].

Basic branching

When working with a centralized workflow the concepts are simple, master represented the official history and is always deployable. With each now scope of work, aka feature, the developer is to create a new branch. For clarity, make sure to use descriptive names like transaction-fail-message or github-oauth for your branches.

	#!/usr/bin/env python

	import email.mime.text
	import smtplib

	username = '[email protected]'
	password = '****************'
	hostname = 'outlook.office365.com'

	msg = email.mime.text.MIMEText('test')

	// Example program
	#include <iostream>
	#include <string>
	#include <memory>

	class singleton
	{
	static std::shared_ptr<singleton> instance(int a)
	{
	if (!instance_)

	from eth.constants import (
	GENESIS_BLOCK_NUMBER,
	GENESIS_DIFFICULTY,
	GENESIS_GAS_LIMIT,
	)

	from eth.db.atomic import (
	AtomicDB,
	)
	from eth.db.chain import (

	from collections import namedtuple
	def convert(dictionary):
	return namedtuple('GenericDict', dictionary.keys())(**dictionary)

	"""
	>>> d = dictionary(a=1, b='b', c=[3])
	>>> named = convert(d)
	>>> named.a == d.a
	True
	>>> named.b == d.b