Typical Git workflow

From RidgeRun Developer Connection
Jump to: navigation, search


Normal workflow is to develop and check in on a branch, then once everything is happy, merge the branch back into the master.

Local repository consists of three "trees" maintained by git. the first one is your Working Directory which holds the actual files.The second one is the Index which acts as a staging area and finally the HEAD which points to the last commit you've made. You typically only see the working directory, but as you issue git commands, it is helpful to understand the information used by git.

Workflow Diagram



Typical Workflow are as follows

  1. get local copy of code
  2. create a branch
  3. edit files
  4. add andcommit changes to local machine
  5. get back in sync with changes commited by others
  6. push branch to remote git repository
  7. merge local branch into local master
  8. push local master to remote git repostiory

The cut-and-paste commands assume you have set REPO and BRANCH shell variables. An example setting would be:


Get a local copy of the code

First create a working directory (what RidgeRun calls a DEVDIR when using a RidgeRun SDK)

git clone $REPO.git sdk

Create a Branch

Branches are used to develop features in isolation from each other. The master branch is the "default" branch when you create a repository. Use other branches for development and merge them back to the master branch upon completion.

Create a new branch and switch to that branch:

git checkout -b $BRANCH

Switch back to master by running the below command:

git checkout master

A branch is not available to the others unless you push the branch to your remote repository

git push origin $BRANCH

Edit Files

Use your favorite editor to modify existing source files and create new source files.

Add and commit changes to a local machine

git creates a commit (very much like a patch file) based on the files you want added to commit.

First you tell git which files you want part of the commit. Any changes you have made to those files will be included in the commit.

git add $FILE1 $FILE2

You can see what files will be part of the next commit, which other files you have changed, and what files have been added that are not part of the git index:

git status

Now you can create the actual commit:

git commit -m "$COMMIT_MESSAGE"

Now the file is committed to the HEAD of your local repository, but the changes are not part of the repository you cloned. However, git will not let you push your commits to the remote repository unless changes commited by others to the remote repository are part of your local repository.

Another helpful command is to see all the commits on your currently checked out branch

gitk &

You may have to run:

sudo apt-get gitk

to install the gitk tool.

Get back in sync with changes commited by others

You first need to get your local master in sync with the remote repository, then merge those changes into your branch.

git checkout master
git pull
git checkout $BRANCH
git merge master

If someone changed a file and pushed that change to the remote repository and you changed the file too in your local repository, then you might need to resolve which changes have priority. There is lots of information on the Internet on how to do this sometimes complex task.

Push branch to remote git repository

You can share your branch with other by pushing it to the remote repository

git push origin $BRANCH

Merge local branch into local master

To merge your branch into your local master:

git checkout master
git merge $BRANCH

git tries to auto-merge changes. Unfortunately, this is not always possible and results in conflicts. You are responsible to merge those conflicts manually by editing the files shown by git. After changing, you need to mark them as merged with

git add $FILE1 $FILE2

before merging changes, you can also preview them by using

git diff $BRANCH master

Push local master to remote git repostiory

To send the changes (from the HEAD of your local master branch) to your remote repository:

git push origin master

Change master to whatever branch you want to push your changes to.