There are now official docs, so follow those as they'll be up-to-date and easier to follow.
  
    
      This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
      Learn more about bidirectional Unicode characters
    
  
  
    
  | #!/usr/bin/python3 | |
| import concurrent.futures | |
| import hashlib | |
| import os | |
| import sys | |
| import gi | |
| gi.require_version('GnomeDesktop', '3.0') | |
| from gi.repository import Gio, GnomeDesktop | 
  
    
      This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
      Learn more about bidirectional Unicode characters
    
  
  
    
  | type | |
| MaybeKind = enum Just, Nothing | |
| Maybe[T] = object | |
| case kind: MaybeKind | |
| of Just: value: T | |
| of Nothing: discard | |
| EitherKind = enum Left, Right | |
| Either[L, R] = object | |
| case kind: EitherKind | 
  
    
      This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
      Learn more about bidirectional Unicode characters
    
  
  
    
  | #!/usr/bin/env lua | |
| local rockspec_name = assert(arg[1]) | |
| local function log(level, fmt, ...) | |
| io.stderr:write(level .. "\t" .. string.format(fmt, ...) .. "\n") | |
| end | |
| local function append(tbl, ...) | |
| for _, v in ipairs {...} do | 
When working with Git, there are two prevailing workflows are Git workflow and feature branches. IMHO, being more of a subscriber to continuous integration, I feel that the feature branch workflow is better suited, and the focus of this article.
If you are new to Git and Git-workflows, I suggest reading the atlassian.com Git Workflow article in addition to this as there is more detail there than presented here.
I admit, using Bash in the command line with the standard configuration leaves a bit to be desired when it comes to awareness of state. A tool that I suggest using follows these instructions on setting up GIT Bash autocompletion. This tool will assist you to better visualize the state of a branc
  
    
      This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
      Learn more about bidirectional Unicode characters
    
  
  
    
  | /** | |
| * Return string representation of MD5 digest of the given message. | |
| * | |
| * @param {String} message Message to be encoded. | |
| * | |
| * @return {String} 16-byte digest value | |
| */ | |
| function signMd5(message){ | |
| return digest(Utilities.DigestAlgorithm.MD5, message); | |
| } |