This document is intended for GitHubers to contribute for Docklet System.
We use fork and pull request workflow to push forward Docklet Project.
Before work, we need to prepare our working repository. These actions should be executed just once.
Open https://github.com/unias/docklet in your browser and click Fork button on the top-right corner.
- clone docklet from your github repository
git clone https://github.com/YourName/docklet.git
- config your local repository
# add unias/docklet as your upstream
git remote add upstream https://github.com/unias/docklet.git
# set push to upstream not work
git remote set-url --push upstream no_push
This part is about the steps of making contributions to Docklet by pull request.
Fetch the latest code from upstream(unias/docklet)
git fetch upstream
Create new branch for your work
git checkout -b BranchName upstream/master
This is not the step you must do and you can work on local master branch. But we recommend you follow these steps. Using branch to develop new features fits git.
Now you can focus on your work by commit and push.
Commit is commit. Nothing to say.
Push your work to your own Github repository by BranchName
git push origin BranchName
After you complete work of this feature, you maybe want to create a pull request to unias/docklet. Please follow steps below.
Fetch the latest code from unias/docklet
git fetch upstream
Merge upstream's latest code to your working branch
git merge upstream/master
Please ensure that you are on your working branch.
If conflict happens, resolve it and commit.
Push to your github repository by BranchName.
git push origin BranchName
Open https://github.com/YourName/docklet, click New pull request and select your working BranchName to create the pull request.
After you fetch upstream code, you can move forward your local master branch to upstream/master. And push your github repository master branch to update.
git fetch upstream
git checkout master
git merge upstream/master
git push origin master
You can config your git log command with pretty format.
git config --global alias.lg "log --graph --color --pretty=format:' %Cred%h %Creset/ %<(10,trunc)%Cblue%an%Creset | %<(60,trunc)%s | %cr %Cred%d' --remotes --branches"
Now, type git lg to see what happens.
Of course, you can use GUI with git. gitg is a good choice. It shows log of git very friendly.
git log has much information. You should understand the log info of git. This can help you know how to move forward your work. Especially the reference of branches : upstream/master, HEAD, master, origin/master, other branches.
The Graphs/Network of Github is very useful. With this, you can know whether you can create a pull request without conflict. Open https://github.com/unias/docklet/network in your browser and see the network graph of docklet.