This tutorial will show you the basics for Git.
For Git to work properly, it needs to store some personal information for use in email merge requests and in the commit logging.
git config --global user.name "Your Name"
git config --global user.email email@example.com
Additionally, to allow colorized output in Git:
git config --global color.ui true
There are other additional color-related features which are discussed in the fine documentation that comes with Git.
If you experience problems with colorized output, try adding the following to your ~/.bashrc
Getting started with Git for KDE is fairly easy. First, run the following:
git clone <REPOSITORY URL>
The <REPOSITORY URL> for the KDE-Qt repository is discussed on the Qt Prerequisites wiki page.
This creates a local copy of the upstream repository. Now change into that directory and code away. When updating, run:
To check the status of the repository. use the status sub-command to view the state of the local copy:
$ git status
nothing added to commit but untracked files present (use "git add" to track)
If 'testfile' should be added to the local copy, run the add sub command:
$ git add testfile
Once 'testfile' has all the changes desired, commit it to the local copy:
$ git commit -m "This is the first commit"
Created initial commit 246d7aa: This is the first commit
1 files changed, 1 insertions(+), 0 deletions(-) create mode 100644 testfile
Much like svn status, if you change a file once it has been committed, running git status will show that the file was modifed since last commit:
$ echo "new content" > testfile
$ git status
no changes added to commit (use "git add" and/or "git commit -a")
As the output states, the changes will not be added to the commit before you use git add to add the files to your staging area. The staging area is a temporary location for the changes to be commited, and it basically allows you to select what files you want to include in a commit. If you want to include all changed files to your next commit, the shortcut "-a" for commit can be used to achieve this.
After the files have been added to the staging area, git diff will not show changes to them. To check your changes before doing the commit, you can pass --cached as an option to diff to see them.
When creating changes to the code from the upstream repository that will later get merged back upstream, branches are highly recommended.
To view the current set of branches available, run git branch. The branch with a proceeding '*' is the active one. To create a new branch called "bugfix-branch" for example, run:
$ git branch bugfix-branch
$ git checkout bugfix-branch
Switched to branch "bugfix-branch"
There is also an alias for that
$ git checkout -b bugfix-branch
Switched to a new branch "bugfix-branch"
Make the necessary changes to the branch and then get ready to merge them back to the master branch
$ git checkout master
Switched to branch "master"
$ git merge bugfix-branch
newfile | 1 + 1 files changed, 1 insertions(+), 0 deletions(-) create mode 100644 newfile
$ ls newfile testfile
If there had been changes made to the branch, git would have automatically tried to merge the changes in the bugfix-branch with the master branch.
Rarely, this can cause a merge conflict. In those cases, manually edit the files that conflict in the master branch, and then do a git commit -a to complete the merge. Git indicates the conflicting lines within the file that cannot be auto-merged.
To view the change log for a given file in the local copy, run git log <FILENAME>.
$ git log testfile
Author: Carsten Niehaus <firstname.lastname@example.org>
Date: Fri Apr 18 18:07:18 2008 +0200
commit 246d7aad05139314e7ff62a5becb6c930f72fb8f Author: Carsten Niehaus <email@example.com> Date: Fri Apr 18 18:06:33 2008 +0200
This is the first commit
To ease the workflow you can use git log -p to see the diffs per commit basis, instead of querying the commit hash with git log and then using git diff against that.