Changes between Version 36 and Version 37 of DevelopmentProcedure


Ignore:
Timestamp:
05/02/14 10:28:52 (11 years ago)
Author:
Jonathan
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • DevelopmentProcedure

    v36 v37  
    1717  git checkout -b ticket_353 development
    1818}}}
    19 1.  Then setup your branch to synchronize with the central repository.
     191.  Then you can setup your branch to synchronize with the central repository.
    2020{{{
    2121  git push -u origin ticket_353
    2222}}}
     23This will allow you to push commits to your local branch to the central repo for others to see and/or use.
     24
    23251. You can then modify code as necessary and then use git add to add any file changes to your next commit
    2426{{{
     
    35371.  You can repeat steps 6-8 as many times as you want until the feature is complete.  Then please notify [mailto:astrobear_dev@pas.rochester.edu] and we will merge your changes into the development branch and the next release.
    3638
     39== Merging ==
     40
     411. To merge 1 branch into another (ie ticket_353 into development) you would do the following
     42{{{
     43git checkout development
     44git merge ticket_353
     45}}}
     461. If there are conflicts you will have to resolve the conflicts, add the conflicted files and commit the merge.
     47{{{
     48git add conflicted_file.f90
     49git commit -m 'merged ticket_353 into development'
     50git push
     51}}}
     521. You can then delete the local branch
     53{{{
     54git branch -d ticket_353
     55}}}
     561. as well as the branch on the central server.
     57{{{
     58git push origin :ticket_353
     59}}}
    3760
    3861[[CollapsibleStart(Previous Procedure)]]