Changes between Version 41 and Version 42 of DevelopmentProcedure


Ignore:
Timestamp:
05/02/14 12:14:23 (11 years ago)
Author:
Jonathan
Comment:

Reverted to version 40.

Legend:

Unmodified
Added
Removed
Modified
  • DevelopmentProcedure

    v41 v42  
    1717  git checkout -b ticket_353 development
    1818}}}
    19 1.  Then you can setup your branch to synchronize with the central repository.
     191. Then you can setup your branch to synchronize with the central repository. This will allow you to push commits to your local branch to the central repo for others to see and/or use.
    2020{{{
    2121  git push -u origin ticket_353
    2222}}}
    23 This will allow you to push commits to your local branch to the central repo for others to see and/or use.
    24 
    25231. You can then modify code as necessary and then use git add to add any file changes to your next commit
    2624{{{
     
    3129  git commit -m "modified zcooling module to write ztable"
    3230}}}
     311. Before you push back to the main repo, you should make sure that your branch is still up to date with the latest development branch
     32{{{
     33  git checkout development
     34  git pull
     35  git checkout ticket_353
     36  git merge development
     37}}}
    33381. And then you can push those changes to the main repo so they don't get lost
    3439{{{
    3540  git push
    3641}}}
    37 1.  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.
     421. You can repeat steps 6-9 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.
    3843
    3944== Merging ==
     
    91961. And then repeat the following steps as needed.
    9297
    93 
    9498[[CollapsibleStart(Previous Procedure)]]
    9599