Commit Policy » 履歴 » バージョン 5
kaoru n, 2014-10-21 13:17
| 1 | 1 | Kousuke Ebihara | h1. Commit Policy |
|---|---|---|---|
| 2 | |||
| 3 | h2. Scope |
||
| 4 | |||
| 5 | This document is only effective in development of OpenPNE3 platform (it doesn't contain plugins). |
||
| 6 | |||
| 7 | h2. Where should you work? |
||
| 8 | |||
| 9 | You have to use your repository on the GitHub. Of course, you can use a repository on your own server if you want to do so. |
||
| 10 | |||
| 11 | 4 | Kousuke Ebihara | In a general rule, you should not directly push to our shared repository, git@github.com:openpne/OpenPNE3.git. Even if you have a priviledge to do it, you should merge from your clone for applying your changes to OpenPNE3. Directly pushing is allowed for a bit changes only. |
| 12 | 1 | Kousuke Ebihara | |
| 13 | h2. Who should you work? |
||
| 14 | |||
| 15 | Everyone. If you want to improve OpenPNE, please do it on your git repository. In doing so, creating branch is good way. |
||
| 16 | 2 | Kousuke Ebihara | |
| 17 | 5 | kaoru n | You finish your improving, please tell it us. Use "Pull Request" on GitHub, or send an email to openpne-dev@ml.pne.jp. We'll check your changes and apply them to OpenPNE3 ASAP. |
| 18 | 2 | Kousuke Ebihara | |
| 19 | h2. How do you integrate with this issue tracking system? |
||
| 20 | |||
| 21 | You should create ticket to manage your changes before you start your work. |
||
| 22 | |||
| 23 | 3 | Kousuke Ebihara | If you want to make relation with your changes and the ticket, you have to include a "refs #1" keyword in the comment message. |
| 24 | 1 | Kousuke Ebihara | |
| 25 | If you finish your work, include a "fixes #1" keyword in your commit message, and a status of the related ticket is changed. |
||
| 26 | 4 | Kousuke Ebihara | |
| 27 | Integrating with this system is applied on pushing to shared repository. |