ITK/Git/Develop: Difference between revisions
No edit summary |
|||
Line 12: | Line 12: | ||
</i> | </i> | ||
== | ==Setup== | ||
Before you begin, perform initial setup: | Before you begin, perform initial setup: | ||
Line 21: | Line 21: | ||
# Run the developer setup script to prepare your ITK work tree and create Git command aliases used below: | # Run the developer setup script to prepare your ITK work tree and create Git command aliases used below: | ||
:<code>$ ./Utilities/SetupForDevelopment.sh</code> | :<code>$ ./Utilities/SetupForDevelopment.sh</code> | ||
==Workflow== | |||
ITK development uses a [[Git/Workflow/Topic|branchy workflow]] based on topic branches. | ITK development uses a [[Git/Workflow/Topic|branchy workflow]] based on topic branches. |
Revision as of 21:30, 16 November 2010
This page documents how to develop ITK through Git.
See our table of contents for more information.
Git is an extremely powerful version control tool that supports many different "workflows" for indivudal development and collaboration. Here we document procedures used by the ITK development community. In the interest of simplicity and brevity we do not provide an explanation of why we use this approach. Furthermore, this is not a Git tutorial. Please see our Git resource links for third-party documentation, such as the ProGit Book.
Setup
Before you begin, perform initial setup:
- Register Gerrit access and possibly Git push access
- Optionally download our one page PDF desk reference
- Follow the download instructions to create a local ITK clone
- Run the developer setup script to prepare your ITK work tree and create Git command aliases used below:
$ ./Utilities/SetupForDevelopment.sh
Workflow
ITK development uses a branchy workflow based on topic branches. Our collaboration workflow consists of three main steps:
- Local Development (requires no special access)
- Code Review (requires Gerrit access)
- Integrate Changes (requires Git push access)
Update
Update your local master branch: | |
|
Create a Topic
Name topics like you might name functions: concise but precise. A reader should have a general idea of the feature or fix to be developed given just the branch name.
To start a new topic branch: | |
|
|
Edit files and create commits (repeat as needed): | |
|
Checkout the topic if it is not your current branch: | |
|
|
Check what commits will be pushed to Gerrit for review: | |
|
( |
Push commits in your topic branch for review by the community: | |
|
( |
Merge a Topic
Checkout the topic if it is not your current branch: | |
|
|
Push the topic to the ITK Topic Stage repository: | |
|
( |
Ask the topic stage repository to merge the topic: | |
|
( |
Delete a Topic
Checkout and update the master branch: | |
|
|
Delete the local topic branch: | |
|
|
The |