-
Notifications
You must be signed in to change notification settings - Fork 15
Development How To
bartaz edited this page Sep 13, 2010
·
20 revisions
This is a document for Taskboard developers that describes development practices. It’s intended to show how do we use Kanban methodology with Git repository.
- story branches – each story or issue should be developed in it’s own branch. This branch should remain local. If there is a need to share the changes with other developers patches should be used (or pulls between developers’ repositories)
-
dev– development branch is intended for code that is still in progress (not yet checked by Product Owner). If the implementation of story/issue is completed it’s branch should be merged dodevbranch. -
done– this should store only fully completed stories/issues. The stories/issues that where indevbranch and where successfully checked by Product Owner should be merged todonebranch. -
master– we usemasterbranch as a release branch – we merge thedevbranch tomasterwhen we do a release
- Clone the repository:
git clone git@github.com:CognifideLabs/taskboard.git
- Go into
taskboarddirectory (all the other commands are done there):cd taskbaord
- Pull
devanddonebranches:git pull origin dev
git pull origin done - Go to
devbranch:git checkout dev
- Delete local
masterbranch (just not to merge something by accident):git branch -d master
- Take the first card from the Queue column
- Move it into In progress column
- Add a tag with you initials to assign this issue to yourself
Create a local branch for the issue (from dev branch).
- Make sure you are in
devbranch:git checkout dev
- Create a branch for the story (let’s call it
story-branch):git branch story-branch
- Move to the story branch:
git checkout story-branch
Do all your development in the story-branch. Here is the list of some git commands that may be useful:
- To check what files are changed:
git status
- To add files to next commit:
git add
- To commit your changes to your local repo (please add issue number to commit message):
git commit -m “#666 this is some evil comment”