Rule of Shared Repository » 履歴 » バージョン 7
Kousuke Ebihara, 2012-11-22 18:52
| 1 | 1 | Kousuke Ebihara | h1. Rule of Shared Repository |
|---|---|---|---|
| 2 | |||
| 3 | h2. Overview |
||
| 4 | |||
| 5 | This document provides rule of handling shared repository of developing OpenPNE3. |
||
| 6 | |||
| 7 | In this document, the "shared repository" means that is git://github.com/openpne/OpenPNE3.git. |
||
| 8 | |||
| 9 | Everyone must follow this rule to handle the shared repository. |
||
| 10 | |||
| 11 | 6 | Kousuke Ebihara | h2. "push" privilege to handle shared repository |
| 12 | 1 | Kousuke Ebihara | |
| 13 | 6 | Kousuke Ebihara | GitHub accounts that are in the following list, can execute "push" operations to shared repository (as of Nov 22, 2012): |
| 14 | 1 | Kousuke Ebihara | |
| 15 | * "balibali":https://github.com/balibali |
||
| 16 | 6 | Kousuke Ebihara | * "ebihara":https://github.com/ebihara |
| 17 | * "imamura623":https://github.com/imamura623 |
||
| 18 | * "kashiwasan":https://github.com/kashiwasan |
||
| 19 | 1 | Kousuke Ebihara | * "kawahara":https://github.com/kawahara |
| 20 | 6 | Kousuke Ebihara | * "martini2002jp":https://github.com/martini2002jp |
| 21 | * "niryuu":https://github.com/niryuu |
||
| 22 | * "nise-nabe":https://github.com/nise-nabe |
||
| 23 | * "ShinichiU":https://github.com/ShinichiU |
||
| 24 | * "tejima":https://github.com/tejima |
||
| 25 | * "touri":https://github.com/touri |
||
| 26 | * "upsilon":https://github.com/upsilon |
||
| 27 | 4 | Kousuke Ebihara | |
| 28 | 6 | Kousuke Ebihara | If you think that you are worthy of getting "push" privilege, please tell your GitHub account to ebihara, balibali, or ShinichiU. |
| 29 | 1 | Kousuke Ebihara | |
| 30 | h2. Committing |
||
| 31 | |||
| 32 | h3. Direct Committing |
||
| 33 | |||
| 34 | Committing direct is not allowed excepting few cases. |
||
| 35 | |||
| 36 | Release Manager can directly commit when he works for releasing. |
||
| 37 | |||
| 38 | In other cases, anyone must work in his own clone. |
||
| 39 | |||
| 40 | h3. Commit Messages |
||
| 41 | |||
| 42 | In merging, commit messages must follow the following rule: |
||
| 43 | * A message must be written in English. A message can contain other languages, but that must be explained in English. |
||
| 44 | 2 | Kousuke Ebihara | * A message must contain related ticket ID. The ID must be specified with "refs" or "fixes" keyword. We have useful hook script for keeping it: http://gist.github.com/202866 |
| 45 | 1 | Kousuke Ebihara | e.g. "Added ability to delete member from the mobile_backend application (refs #1)", "Added ability to configure gadgets from the mobile_backend application. Adding support to manage SNS from mobile is now completed. (fixes #1)" |
| 46 | * A message must tell everyone what the commit is. |
||
| 47 | |||
| 48 | A commit that doesn't follow this rule, most likely is rejected. |
||
| 49 | |||
| 50 | h2. Merging |
||
| 51 | |||
| 52 | If you developed something or got "Pull Request", please merge it. After merging, you must check changes. If the changes has some faults, contact author about it to fix them. |
||
| 53 | |||
| 54 | 3 | Kousuke Ebihara | If changes looks fine, push it to shared repository, and change a status of the related ticket to "Pending Review". (Changing status is doing automatically if a commit is related with a ticket by the "fixes" keyword in its message) |
| 55 | 5 | Kousuke Ebihara | |
| 56 | h2. Branches |
||
| 57 | |||
| 58 | Branches of the shared repository must limit the release branches (they contain the master branch). Don't push a branch for your work. You should create such a branch to your repository. |