Skip to content

Commit

Permalink
[Improvement] Update submit-code.md (#256)
Browse files Browse the repository at this point in the history
  • Loading branch information
davidzollo authored Aug 31, 2023
1 parent 2033512 commit e106f96
Showing 1 changed file with 7 additions and 7 deletions.
14 changes: 7 additions & 7 deletions community/submit_guide/submit-code.md
Original file line number Diff line number Diff line change
Expand Up @@ -5,25 +5,25 @@ sidebar_position: 2

# Submit Code

* First from the remote repository <https://github.com/apache/incubator-seatunnel.git> fork a copy of the code into your own repository
* First from the remote repository <https://github.com/apache/seatunnel.git> fork a copy of the code into your own repository

* There are currently three branches in the remote repository:
* **dev** daily development branch
> Every day dev development branch, newly submitted code can pull request to this branch.
* **1.0.0-release** release version branch
> The release version branch, there will be 2.0...and other version branches in the future.
* **3.2.0-release** release version branch
> The release version branch, there will be 4.0...and other version branches in the future.
* Clone your repository to your local

```shell
git clone git@github.com:apache/incubator-seatunnel.git
git clone https://github.com/apache/seatunnel
```

* Add remote repository address, named upstream

```shell
git remote add upstream git@github.com:apache/incubator-seatunnel.git
git remote add upstream https://github.com/apache/seatunnel
```

* View repository
Expand All @@ -50,7 +50,7 @@ sidebar_position: 2
* If remote branch has a new branch such as `dev-1.0`, you need to synchronize this branch to the local repository

```shell
git checkout -b dev-1.0 upstream/dev-1.0
git checkout -b dev upstream/dev-1.0
git push --set-upstream origin dev-1.0
```

Expand All @@ -69,4 +69,4 @@ sidebar_position: 2

* Then the community Committers will do CodeReview, and then he will discuss some details (including design, implementation, performance, etc.) with you. When everyone on the team is satisfied with this modification, the commit will be merged into the dev branch

* Finally, congratulations, you have become an official contributor to Apache Seatunnel !
* Finally, congratulations, you have become an official contributor to Apache SeaTunnel !

0 comments on commit e106f96

Please sign in to comment.