Difference between revisions of "Typical Git workflow"

From RidgeRun Developer Connection
Jump to: navigation, search
m
m
 
(26 intermediate revisions by 3 users not shown)
Line 1: Line 1:
 
== Introduction  ==
 
== Introduction  ==
  
Normal workflow is to develop and check in on a branch, then once everything is happy, merge the branch back into the master. 
+
The 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.  
+
The 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  ==
+
== Workflow Diagram  ==
  
 
[[Image:Git-workflow.png]]
 
[[Image:Git-workflow.png]]
  
== References<br> ==
+
== References  ==
  
<span style="line-height: 1.5em;">[https://confluence.atlassian.com/display/STASH/Basic+Git+commands https://confluence.atlassian.com/display/STASH/Basic+Git+commands]</span>
+
* Basic Git Commands : [https://confluence.atlassian.com/display/STASH/Basic+Git+commands https://confluence.atlassian.com/display/STASH/Basic+Git+commands]
 +
* Git- The Simple Guide: [http://rogerdudler.github.io/git-guide/ http://rogerdudler.github.io/git-guide]
 +
* Basic Git Commands : [http://robert-reiz.com/2011/10/01/git-add-commit-push-pull/ http://robert-reiz.com/2011/10/01/git-add-commit-push-pull]
  
[http://rogerdudler.github.io/git-guide/ http://rogerdudler.github.io/git-guide/]
+
== Typical Workflow are as follows  ==
 +
 
 +
# Get local copy of code
 +
# Create a branch
 +
# Edit files
 +
# Add and commit changes to local machine
 +
# Get back in sync with changes commited by others
 +
# Push branch to remote git repository
 +
# Merge local branch into local master
 +
# 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:
 +
 
 +
<pre>
 +
REPO=git@github.com:RidgeRun/eval-sdk-dm36x
 +
BRANCH=fixed-ip-address
 +
</pre>
 +
 
 +
== Get a local copy of the code  ==
 +
 
 +
First, create a working directory (what RidgeRun calls a DEVDIR when using a RidgeRun SDK)
 +
 
 +
<pre>
 +
git clone $REPO.git sdk
 +
</pre>
 +
 
 +
== Create a Branch  ==
  
[http://robert-reiz.com/2011/10/01/git-add-commit-push-pull/ http://robert-reiz.com/2011/10/01/git-add-commit-push-pull/]
+
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.  
  
== Typical Workflow are as follows  ==
+
Create a new branch and switch to that branch:
 +
 
 +
<pre>
 +
git checkout -b $BRANCH
 +
</pre>
 +
 
 +
Switch back to master by running the below command:
 +
 
 +
<pre>
 +
git checkout master
 +
</pre>
  
1) get local copy of code<br>2) create a branch<br>3) edit files<br>4) add/commit changes to local machine<br>5) get back in sync with changes commited by others<br>6) push branch to remote git repository<br>7) merge local branch into local master<br>8) push local master to remote git repostiory
+
A branch is not available to the others unless you push the branch to your remote repository  
  
<br>  
+
<pre>
 +
git push origin $BRANCH
 +
</pre>
  
'''For the TATAPowersed SDK we can set REPO and BRANCH as below:'''
+
== Edit Files ==
<pre>REPO=git@github.com:RidgeRun/tata-sdk-dm36x
 
BRANCH=fixed-ip-address</pre>
 
  
== 1) Get&nbsp;a local copy of the code  ==
+
Use your favorite editor to modify existing source files and create new source files.
<pre>git clone $REPO.git tatasdk
 
  
OR
+
== Add and commit changes to a local machine  ==
  
git clone https://github.com/RidgeRun/tata-sdk-dm36x.git tatasdk
+
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.
 +
 +
<pre>
 +
git add $FILE1 $FILE2
 
</pre>
 
</pre>
Creating the Working copy of the local repository by running the command:
 
<pre>git clone path/to/repository</pre>
 
  
== 2) Create a Branch  ==
+
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:
  
Branches are used to develop features isolated from each other. The master branch is the "default" branch when you create a repository. <br>Use other branches for development and merge them back to the master branch upon completion.
+
<pre>
 +
git status
 +
</pre>
  
Create a new branch named tatasdk1 and switch to it using below command:  
+
Now you can create the actual commit:
<pre>git checkout -b tatasdk1
+
 +
<pre>
 +
git commit -m "$COMMIT_MESSAGE"
 
</pre>  
 
</pre>  
Switch back to master by running the below command:  
+
 
<pre>git checkout master
+
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 committed 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
 +
 
 +
<pre>
 +
gitk &
 +
</pre>
 +
 
 +
You may have to run:
 +
 
 +
<pre>
 +
sudo apt-get gitk
 +
</pre>
 +
 
 +
to install the gitk tool.
 +
 
 +
== Get back in sync with changes committed by others ==
 +
 
 +
You first need to get your local master in sync with the remote repository, then merge those changes into your branch.
 +
 
 +
<pre>
 +
git checkout master
 +
git pull
 +
git checkout $BRANCH
 +
git merge master
 +
</pre>
 +
 
 +
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 the branch to remote git repository ==
 +
 
 +
You can share your branch with others by pushing it to the remote repository
 +
 
 +
<pre>
 +
git push origin $BRANCH
 +
</pre>
 +
 
 +
== Merge local branch into local master  ==
 +
 
 +
To merge your branch into your local master:
 +
 
 +
<pre>
 +
git checkout master
 +
git merge $BRANCH
 
</pre>  
 
</pre>  
And delete the branch again:
+
 
<pre>git branch -d tatasdk1
+
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
 +
 +
<pre>
 +
git add $FILE1 $FILE2
 
</pre>  
 
</pre>  
A Branch is not available to the others unless you push the branch to your remote repository
 
<pre>git push origin &lt;branch&gt;
 
</pre>
 
== 3) Add Files<br>  ==
 
  
== 4) Add / Commit changes to a Local Machine  ==
+
before merging changes, you can also preview them by using
  
You can propose changes (add it to the Index) using <br>  
+
<pre>
<pre>git add &lt;filename&gt;
+
git diff $BRANCH master
</pre><pre>git add * </pre>  
+
</pre>
This is the first step in the basic git workflow. To actually commit these changes use:<br>
+
 
<pre>git commit -m "Commit message"
+
== Push local master to remote git repository ==
</pre>
 
Now the file is committed to the HEAD, but not in your remote repository yet.<br>
 
  
'''Pushing Changes:'''<br>
+
To send the changes (from the HEAD of your local master branch) to your remote repository:
  
Your changes are now in the HEAD of your local working copy. To send those changes to your remote repository, execute
+
<pre>
<pre>git push origin master
+
git push origin master
 
</pre>  
 
</pre>  
Change master to whatever branch you want to push your changes to.<br>
 
  
== 5) Get back in sync with changes commited by others ==
+
Change master to whatever branch you want to push your changes to.
 +
 
 +
[[Category:Git]][[Category:HowTo]][[Category:GitHub]][[Category:GitLab]]

Latest revision as of 23:24, 18 February 2021

Introduction

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

The 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

Error creating thumbnail: Unable to save thumbnail to destination

References

Typical Workflow are as follows

  1. Get local copy of code
  2. Create a branch
  3. Edit files
  4. Add and commit 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:

REPO=git@github.com:RidgeRun/eval-sdk-dm36x
BRANCH=fixed-ip-address

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 committed 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 committed 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 the branch to remote git repository

You can share your branch with others 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 repository

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.