Development cycle » History » Version 1
Tom Clegg, 06/08/2011 03:54 PM
1 | 1 | Tom Clegg | h1. Development cycle |
---|---|---|---|
2 | |||
3 | h2. Writing and contributing code |
||
4 | |||
5 | Start a branch like username/master or username/rails3 |
||
6 | |||
7 | git branch example/rails3 |
||
8 | git checkout example/rails3 |
||
9 | |||
10 | Do something trivial like |
||
11 | |||
12 | * add app/views/pages/specimen_collection.html.erb |
||
13 | * add link to it in app/views/pages/home.html.erb |
||
14 | |||
15 | Commit it |
||
16 | |||
17 | git add ... |
||
18 | git commit -m '...' |
||
19 | |||
20 | Push it |
||
21 | |||
22 | git push |
||
23 | |||
24 | Generate a pull request |
||
25 | |||
26 | git request-pull e68ab19^ git@git.clinicalfuture.com:pgp-enroll.git e68ab19 |
||
27 | |||
28 | Send the pull request to someone like Ward |
||
29 | |||
30 | h2. Merging code from other contributors/branches |
||
31 | |||
32 | Get latest stuff |
||
33 | |||
34 | git pull |
||
35 | |||
36 | Check out master branch (or whatever branch you want to pull the new code into) |
||
37 | |||
38 | git checkout master |
||
39 | |||
40 | Cherry-pick a commit |
||
41 | |||
42 | git cherry-pick e68ab19 |
||
43 | |||
44 | Push |
||
45 | |||
46 | git push |