Guest User

Untitled

a guest
Jun 20th, 2018
80
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 3.61 KB | None | 0 0
  1. h2. Feature Development
  2.  
  3. h3. Basic Steps
  4.  
  5. <ol>
  6. <li>Pull to update your local Release Branch</li>
  7. <li>Check out a feature branch</li>
  8. <li>Do work in your feature branch, committing early and often</li>
  9. <li>Rebase frequently to incorporate upstream changes</li>
  10. <li>Interactive rebase (squash) your commits</li>
  11. <li>Notify QA of your completed feature</li>
  12. <li>Once your feature has been approved by QA</li>
  13. <ol>
  14. <li>Rebase once again from the Release Branch</li>
  15. <li>Merge your changes into the Release Branch</li>
  16. <li>Push your changes upstream</li>
  17. </ol>
  18. </ol>
  19.  
  20. h3. Steps in Depth
  21.  
  22.  
  23. h4. Background Info
  24.  
  25. The Release Branch is *RB_10_29_2010*
  26. _My Name is Lorgio Jimenez_
  27. _My initial are *lj*_
  28. _my agile buddy feature is *O1477*_
  29.  
  30. h4. Before you begin you must use this command
  31.  
  32. bq. git config branch.autosetuprebase always
  33.  
  34. The code above will make your git pull command default to always add --rebase
  35.  
  36.  
  37. <ol>
  38. <li>
  39. h4. +Pull to update your local Release Branch+
  40.  
  41.  
  42. @git checkout --track origin/RB_10_29_2010@
  43. @git pull origin RB_10_29_2010@
  44.  
  45. <p>this will create a local branch named RB_10_29_2010</p>
  46. </li>
  47. <li>
  48. h4. +Check out a feature branch+
  49.  
  50. @git checkout -b lj_O1477_nav_menus@
  51.  
  52. <p>_*My Initials + agile buddy ticket + small description*_</p>
  53. </li>
  54. <li>
  55. h4. +Do work in your feature branch, committing early and often+
  56.  
  57.  
  58. @#do your work@
  59. @git add foo.rb@
  60. @git commit -m "WIP: hacking on this and that"@
  61. @#do more work@
  62. @git add -p bar.rb@
  63.  
  64. </li>
  65. <li>
  66. h4. +Rebase frequently to incorporate upstream changes+
  67.  
  68.  
  69. @git fetch origin RB_10_29_2010@
  70. @git rebase origin/RB_10_29_2010@
  71.  
  72. </li>
  73. <li>
  74. h4. +Interactive rebase (squash) your commits+
  75.  
  76. @git rebase -i origin/RB_10_29_2010@
  77.  
  78. <h5>
  79. *Git will display an editor window with a list of the commits to be modified, something like:*
  80.  
  81. @pick 3dcd585 Adding Comment model, migrations, spec @
  82. @pick 9f5c362 Adding Comment controller, helper, spec@
  83. @pick dcd4813 Adding Comment relationship with Post@
  84. @pick 977a754 Comment belongs to a User@
  85. @pick 9ea48e3 Comment form on Post show page@
  86.  
  87. *Now we tell git what we to do. Change these lines to:*
  88.  
  89. @pick 3dcd585 Adding Comment model, migrations, spec@
  90. @squash 9f5c362 Adding Comment controller, helper, spec@
  91. @squash dcd4813 Adding Comment relationship with Post@
  92. @squash 977a754 Comment belongs to a User@
  93. @squash 9ea48e3 Comment form on Post show page@
  94.  
  95. </h5>
  96. </li>
  97. <li>
  98. h4. +Notify QA of your completed feature+
  99.  
  100. h5. you can do this by updating your agile buddy ticket and adding a comment that the feature has been completed. Add ALL the QA members, Laura Manni & Rodney Woodruff to the message
  101. </li>
  102. <li>
  103. h4. +Once your feature has been approved by QA+
  104. </li>
  105. <ol>
  106. <li>
  107. h4. +Rebase once again from the Release Branch+
  108.  
  109.  
  110. @git fetch origin RB_10_29_2010@
  111. @git rebase origin/RB_10_29_2010@
  112.  
  113. </li>
  114. <li>
  115. h4. +Merge your changes into the Release Branch+
  116.  
  117.  
  118. @git checkout RB_10_29_2010@
  119. @git merge lj_O1477_nav_menus@
  120.  
  121. </li>
  122. <li>
  123. h4. +Push your changes upstream+
  124.  
  125.  
  126. @git push origin RB_10_29_2010@
  127.  
  128. </li>
  129. </ol>
  130. </ol>
  131.  
  132.  
  133. h2. Feature Development with multiple users
  134.  
  135. h4. push your local branch to github
  136.  
  137. @git push origin branch_name@
  138. @git branch --set-upstream branch_name origin/branch_name@
  139.  
  140. h5. Then, others can check out your changes with a git fetch and a git checkout.
  141.  
  142. @git fetch@
  143. @git checkout --track origin/branch_name@
  144.  
  145. h5. Use the same exact steps as above and ONLY you should NEVER rebase a commit that has already been pushed remotely.
  146.  
  147.  
  148.  
  149. h2. BugFixes
  150.  
  151. h4. The only difference from the steps above is
  152.  
  153. <ul>
  154. <li>Use the master branch instead of the release branch</li>
  155. <li>ONLY have ONE commit(squashed)</li>
  156. <li>do NOT have a partial fix</li>
  157. </ul>
Add Comment
Please, Sign In to add comment