FRAT/Development: Difference between revisions
From KitwarePublic
< FRAT
Jump to navigationJump to search
Line 29: | Line 29: | ||
= Development Guidelines = | = Development Guidelines = | ||
Current development on FRAT is done using [http://git-scm.com/ git]. The repository is currently hosted at: | Current development on FRAT is done using [http://git-scm.com/ git]. The repository is currently hosted at: | ||
* https://gitorious.org/frat | * https://gitorious.org/frat/frat | ||
== Development Environment == | == Development Environment == | ||
To gain write access to the repository, contact one of the [[FRAT/Team administrators]]. Once gained, follow the steps in the [[FRAT/Install_Guide | Installation Guide]] except use the read/write address to clone the repository | |||
git clone git@gitorious.org:frat/frat.git | |||
== Workflow == | == Workflow == |
Revision as of 20:30, 10 August 2011
__NOTITLE__
|
Development GuidelinesCurrent development on FRAT is done using git. The repository is currently hosted at: Development EnvironmentTo gain write access to the repository, contact one of the FRAT/Team administrators. Once gained, follow the steps in the Installation Guide except use the read/write address to clone the repository git clone git@gitorious.org:frat/frat.git WorkflowDue to the small developer community, we follow a simple branchy workflow in git. The core workflow is:
git checkout master git checkout -b MY_TOPIC
<edit files> git commit -a <Add descriptive commit message>
git checkout master git merge --no-ff --log MY_TOPIC
git push NOTE: For minor bug fixes, commits directly onto master are ok. In this case, make sure that the commit message reads something like: BUG: brief bug description This is a full description of the bug and what I did to fix it. |