プロジェクト

全般

プロフィール

Commit Policy » 履歴 » バージョン 3

Kousuke Ebihara, 2009-10-05 01:43
ref -> refs

1 1 Kousuke Ebihara
h1. Commit Policy
2 1 Kousuke Ebihara
3 1 Kousuke Ebihara
h2. Scope
4 1 Kousuke Ebihara
5 1 Kousuke Ebihara
This document is only effective in development of OpenPNE3 platform (it doesn't contain plugins). 
6 1 Kousuke Ebihara
7 1 Kousuke Ebihara
h2. Where should you work?
8 1 Kousuke Ebihara
9 1 Kousuke Ebihara
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 1 Kousuke Ebihara
11 1 Kousuke Ebihara
In a general rule, you should not directly push to git@github.com:openpne/OpenPNE3.git. Even if you have a priviledge to do it, you should use "Pull Requests" from your branch for applying your changes to OpenPNE3. Directly pushing is allowed for a bit changes only.
12 1 Kousuke Ebihara
13 1 Kousuke Ebihara
h2. Who should you work?
14 1 Kousuke Ebihara
15 1 Kousuke Ebihara
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 2 Kousuke Ebihara
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 2 Kousuke Ebihara
h2. How do you integrate with this issue tracking system?
20 2 Kousuke Ebihara
21 2 Kousuke Ebihara
You should create ticket to manage your changes before you start your work.
22 2 Kousuke Ebihara
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 2 Kousuke Ebihara
25 2 Kousuke Ebihara
If you finish your work, include a "fixes #1" keyword in your commit message, and a status of the related ticket is changed.