lobner

Keybase proof

I hereby claim:

• I am lobner on github.
• I am lobner (https://keybase.io/lobner) on keybase.
• I have a public key ASB-zARrm916QduzoWvApmwTZImv_OcOlCit5JbgUheWPAo

To claim this, I am signing this object:

lobner

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.

lobner

#!/bin/bash

# A simple script to pull a repo off an old host 
# (such as git@git.example.com:repo1.git)
# and import it as private repo to github organization 
# (git@github.com:example_organization/repo1.git)


# Example Usage ==>     ./github-import.sh repo1 repo2 repo3