ITK/Git/Account: Difference between revisions
From KitwarePublic
Jump to navigationJump to search
No edit summary |
No edit summary |
||
Line 4: | Line 4: | ||
=Gerrit= | =Gerrit= | ||
Anyone may | Anyone may obtain access to the [http://review.source.kitware.com/p/ITK ITK Gerrit Code Review] site to propose and review changes. | ||
Follow these steps to set up access: | Follow these steps to set up access: | ||
Revision as of 16:59, 10 November 2015
This page documents how to setup ITK developer accounts. See our table of contents for more information.
Gerrit
Anyone may obtain access to the ITK Gerrit Code Review site to propose and review changes. Follow these steps to set up access:
- We use Github OAuth, so sign in to your Github account
- Sign in to http://review.source.kitware.com using the link in the upper right and approve when Github prompts
- Set all fields in your profile at http://review.source.kitware.com/#/settings/
- Add your ssh public key at http://review.source.kitware.com/#/settings/ssh-keys
Firewall blocks SSH traffic
If you are stuck behind a firewall that blocks SSH traffic (port 22), the following alternative URL may be used to push patches over HTTP (port 80):
- For Gerrit user bob:
$ git config --global url.http://bob@review.source.kitware.com/p/ITK.insteadOf bob@review.source.kitware.com:ITK
- Generate a password at http://review.source.kitware.com/#/settings/http-password
- A password prompt will be presented when pushing patches to Gerrit.
This requires Git 1.6.6 or newer.
Git
Authorized community members may merge patches to the itk.org
repositories, but most community members do not need merge permissions. All patches from all community members go through Gerrit Code Review, and patches will be merged by one of the maintainers after it has been reviewed.
Follow these steps to set up access:
- Submit your ssh public key to the Kitware Password form
- Perform an authentication test:
$ ssh git@itk.org info