You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: CONTRIBUTING.md
+15-15
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
-
# Contributing to Seata
1
+
# Contributing to Apache Seata(incubating)
2
2
3
-
It is warmly welcomed if you have interest to hack on Seata. First, we encourage this kind of willing very much. And here is a list of contributing guide for you.
3
+
It is warmly welcomed if you have interest to hack on Apache Seata(incubating). First, we encourage this kind of willing very much. And here is a list of contributing guide for you.
4
4
5
5
[[中文贡献文档](./CONTRIBUTING_CN.md)]
6
6
@@ -15,11 +15,11 @@ It is warmly welcomed if you have interest to hack on Seata. First, we encourage
15
15
16
16
## Reporting security issues
17
17
18
-
Security issues are always treated seriously. As our usual principle, we discourage anyone to spread security issues. If you find a security issue of Seata, please do not discuss it in public and even do not open a public issue. Instead we encourage you to send us a private email to [[email protected]](mailto:[email protected]) to report this.
18
+
Security issues are always treated seriously. As our usual principle, we discourage anyone to spread security issues. If you find a security issue of Apache Seata(incubating), please do not discuss it in public and even do not open a public issue. Instead we encourage you to send us a private email to [[email protected]](mailto:[email protected]) to report this.
19
19
20
20
## Reporting general issues
21
21
22
-
To be honest, we regard every user of Seata as a very kind contributor. After experiencing Seata, you may have some feedback for the project. Then feel free to open an issue via [NEW ISSUE](https://github.com/seata/seata/issues/new/choose).
22
+
To be honest, we regard every user of Seata as a very kind contributor. After experiencing Seata, you may have some feedback for the project. Then feel free to open an issue via [NEW ISSUE](https://github.com/apache/incubator-seata/issues/new/choose).
23
23
24
24
Since we collaborate project Seata in a distributed way, we appreciate **WELL-WRITTEN**, **DETAILED**, **EXPLICIT** issue reports. To make the communication more efficient, we wish everyone could search if your issue is an existing one in the searching list. If you find it existing, please add your details in comments under the existing issue instead of opening a brand new one.
25
25
@@ -70,36 +70,36 @@ Since you are ready to improve Seata with a PR, we suggest you could take a look
70
70
71
71
To put forward a PR, we assume you have registered a GitHub ID. Then you could finish the preparation in the following steps:
72
72
73
-
1.**FORK** Seata to your repository. To make this work, you just need to click the button Fork in right-left of [seata/seata](https://github.com/seata/seata) main page. Then you will end up with your repository in `https://github.com/<your-username>/seata`, in which `your-username` is your GitHub username.
73
+
1.**FORK** Seata to your repository. To make this work, you just need to click the button Fork in right-left of [apache/incubator-seata](https://github.com/apache/incubator-seata) main page. Then you will end up with your repository in `https://github.com/<your-username>/incubator-seata`, in which `your-username` is your GitHub username.
74
74
75
-
1.**CLONE** your own repository to develop locally. Use `git clone [email protected]:<your-username>/seata.git` to clone repository to your local machine. Then you can create new branches to finish the change you wish to make.
75
+
1.**CLONE** your own repository to develop locally. Use `git clone [email protected]:<your-username>/incubator-seata.git` to clone repository to your local machine. Then you can create new branches to finish the change you wish to make.
76
76
77
-
1.**Set Remote** upstream to be `[email protected]:seata/seata.git` using the following two commands:
77
+
1.**Set Remote** upstream to be `[email protected]:apache/incubator-seata.git` using the following two commands:
Adding this, we can easily synchronize local branches with upstream branches.
95
95
96
96
### Branch Definition
97
97
98
-
Right now we assume every contribution via pull request is for [branch develop](https://github.com/seata/seata/tree/develop) in Seata. Before contributing, be aware of branch definition would help a lot.
98
+
Right now we assume every contribution via pull request is for [branch develop](https://github.com/apache/incubator-seata/tree/2.x) in Seata. Before contributing, be aware of branch definition would help a lot.
99
99
100
100
As a contributor, keep in mind again that every contribution via pull request is for branch develop. While in project Seata, there are several other branches, we generally call them release branches(such as 0.6.0,0.6.1), feature branches, hotfix branches and master branch.
101
101
102
-
When officially releasing a version, there will be a release branch and named with the version number.
102
+
When officially releasing a version, there will be a release branch and named with the version number.
103
103
104
104
After the release, we will merge the commit of the release branch into the master branch.
0 commit comments