-
Notifications
You must be signed in to change notification settings - Fork 286
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
optimize: rename module name to seata.apache.org/seata-go (#678)
- Loading branch information
Showing
240 changed files
with
1,011 additions
and
1,014 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -14,7 +14,7 @@ It is warmly welcomed if you have interest to hack on seata-go. First, we encour | |
|
||
## Reporting general issues | ||
|
||
To be honest, we regard every user of seata-go as a very kind contributor. After experiencing seata-go, you may have some feedback for the project. Then feel free to open an issue via [NEW ISSUE](https://github.com/seata/seata-go/issues/new/choose). | ||
To be honest, we regard every user of seata-go as a very kind contributor. After experiencing seata-go, you may have some feedback for the project. Then feel free to open an issue via [NEW ISSUE](https://github.com/apache/incubator-seata-go/issues/new/choose). | ||
|
||
Since we collaborate project seata-go 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. | ||
|
||
|
@@ -65,14 +65,14 @@ Since you are ready to improve seata-go with a PR, we suggest you could take a l | |
|
||
To put forward a PR, we assume you have registered a GitHub ID. Then you could finish the preparation in the following steps: | ||
|
||
1. **FORK** seata-go 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-go) main page. Then you will end up with your repository in `https://github.com/<your-username>/seata-go`, in which `your-username` is your GitHub username. | ||
1. **FORK** seata-go to your repository. To make this work, you just need to click the button Fork in right-left of [seata/seata](https://github.com/apache/incubator-seata-go) main page. Then you will end up with your repository in `https://github.com/<your-username>/seata-go`, in which `your-username` is your GitHub username. | ||
|
||
1. **CLONE** your own repository to develop locally. Use `git clone [email protected]:<your-username>/seata-go.git` to clone repository to your local machine. Then you can create new branches to finish the change you wish to make. | ||
|
||
1. **Set Remote** upstream to be `[email protected]:seata/seata-go.git` using the following two commands: | ||
1. **Set Remote** upstream to be `[email protected]:apache/seata-go.git` using the following two commands: | ||
|
||
```bash | ||
git remote add upstream [email protected]:seata/seata-go.git | ||
git remote add upstream [email protected]:apache/seata-go.git | ||
git remote set-url --push upstream no-pushing | ||
``` | ||
|
||
|
@@ -82,15 +82,15 @@ With this remote setting, you can check your git remote configuration like this: | |
$ git remote -v | ||
origin [email protected]:<your-username>/seata-go.git (fetch) | ||
origin [email protected]:<your-username>/seata-go.git (push) | ||
upstream [email protected]:seata/seata-go.git (fetch) | ||
upstream [email protected]:apache/seata-go.git (fetch) | ||
upstream no-pushing (push) | ||
``` | ||
|
||
Adding this, we can easily synchronize local branches with upstream branches. | ||
|
||
### Branch Definition | ||
|
||
Right now we assume every contribution via pull request is for [branch develop](https://github.com/seata/seata-go/tree/develop) in seata-go. Before contributing, be aware of branch definition would help a lot. | ||
Right now we assume every contribution via pull request is for [branch develop](https://github.com/apache/incubator-seata-go/tree/master) in seata-go. Before contributing, be aware of branch definition would help a lot. | ||
|
||
As a contributor, keep in mind again that every contribution via pull request is for branch develop. While in project seata-go, 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. | ||
|
||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -14,7 +14,7 @@ | |
|
||
## 报告一般问题 | ||
|
||
老实说我们把每一个 seata-go 用户都视为非常善良的贡献者。在体验了 seata-go 之后,您可能会对项目有一些反馈。然后随时通过 [NEW ISSUE](https://github.com/seata/seata-go/issues/new/choose)打开一个问题。 | ||
老实说我们把每一个 seata-go 用户都视为非常善良的贡献者。在体验了 seata-go 之后,您可能会对项目有一些反馈。然后随时通过 [NEW ISSUE](https://github.com/apache/incubator-seata-go/issues/new/choose)打开一个问题。 | ||
|
||
因为我们在一个分布式的方式合作项目 seata-go,我们欣赏写得很好的,详细的,准确的问题报告。为了让沟通更高效,我们希望每个人都可以搜索您的问题是否在搜索列表中。如果您发现它存在,请在现有问题下的评论中添加您的详细信息,而不是打开一个全新的问题。 | ||
|
||
|
@@ -65,14 +65,14 @@ | |
|
||
为了提出 PR,我们假设你已经注册了一个 GitHub ID。然后您可以通过以下步骤完成准备工作: | ||
|
||
1. **FORK** seata-go 到您的存储库。要完成这项工作,您只需单击 [seata/seata-go](https://github.com/seata/seata-go) 主页右侧的 Fork 按钮。然后你将在 中得到你的存储库`https://github.com/<your-username>/seata-go`,其中 your-username 是你的 GitHub 用户名。 | ||
1. **FORK** seata-go 到您的存储库。要完成这项工作,您只需单击 [apache/seata-go](https://github.com/apache/incubator-seata-go) 主页右侧的 Fork 按钮。然后你将在 中得到你的存储库`https://github.com/<your-username>/seata-go`,其中 your-username 是你的 GitHub 用户名。 | ||
|
||
2. **克隆** 您自己的存储库以在本地开发. 用于 `git clone [email protected]:<your-username>/seata-go.git` 将存储库克隆到本地计算机。 然后您可以创建新分支来完成您希望进行的更改。 | ||
|
||
3. **设置远程** 将上游设置为 `[email protected]:seata/seata-go.git` 使用以下两个命令: | ||
3. **设置远程** 将上游设置为 `[email protected]:apache/seata-go.git` 使用以下两个命令: | ||
|
||
```bash | ||
git remote add upstream [email protected]:seata/seata-go.git | ||
git remote add upstream [email protected]:apache/seata-go.git | ||
git remote set-url --push upstream no-pushing | ||
``` | ||
|
||
|
@@ -82,15 +82,15 @@ git remote set-url --push upstream no-pushing | |
$ git remote -v | ||
origin [email protected]:<your-username>/seata-go.git (fetch) | ||
origin [email protected]:<your-username>/seata-go.git (push) | ||
upstream [email protected]:seata/seata-go.git (fetch) | ||
upstream [email protected]:apache/seata-go.git (fetch) | ||
upstream no-pushing (push) | ||
``` | ||
|
||
添加这个,我们可以轻松地将本地分支与上游分支同步。 | ||
|
||
### 分支定义 | ||
|
||
现在我们假设通过拉取请求的每个贡献都是针对 seata-go 中的 [开发分支](https://github.com/seata/seata-go/tree/master) 。在贡献之前,请注意分支定义会很有帮助。 | ||
现在我们假设通过拉取请求的每个贡献都是针对 seata-go 中的 [开发分支](https://github.com/apache/incubator-seata-go/tree/master) 。在贡献之前,请注意分支定义会很有帮助。 | ||
|
||
作为贡献者,请再次记住,通过拉取请求的每个贡献都是针对分支开发的。而在 seata-go 项目中,还有其他几个分支,我们一般称它们为 release 分支(如0.6.0、0.6.1)、feature 分支、hotfix 分支和 master 分支。 | ||
|
||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.