Skip to content
体验新版
项目
组织
正在加载...
登录
切换导航
打开侧边栏
DolphinScheduler社区
DolphinScheduler
提交
da6a073c
DolphinScheduler
项目概览
DolphinScheduler社区
/
DolphinScheduler
与 Fork 源项目一致
Fork自
apache / DolphinScheduler
通知
67
Star
1
Fork
0
代码
文件
提交
分支
Tags
贡献者
分支图
Diff
Issue
0
列表
看板
标记
里程碑
合并请求
0
Wiki
0
Wiki
分析
仓库
DevOps
项目成员
Pages
DolphinScheduler
项目概览
项目概览
详情
发布
仓库
仓库
文件
提交
分支
标签
贡献者
分支图
比较
Issue
0
Issue
0
列表
看板
标记
里程碑
合并请求
0
合并请求
0
Pages
分析
分析
仓库分析
DevOps
Wiki
0
Wiki
成员
成员
收起侧边栏
关闭侧边栏
动态
分支图
创建新Issue
提交
Issue看板
体验新版 GitCode,发现更多精彩内容 >>
未验证
提交
da6a073c
编写于
7月 29, 2019
作者:
E
easyscheduler
提交者:
GitHub
7月 29, 2019
浏览文件
操作
浏览文件
下载
电子邮件补丁
差异文件
Update CONTRIBUTING.md
上级
fba74eb4
变更
1
隐藏空白更改
内联
并排
Showing
1 changed file
with
80 addition
and
13 deletion
+80
-13
CONTRIBUTING.md
CONTRIBUTING.md
+80
-13
未找到文件。
CONTRIBUTING.md
浏览文件 @
da6a073c
EasyScheduler提交代码流程
=====
*
First from the remote repository
*https://github.com/analysys/EasyScheduler.git*
fork code to your own repository
*
there are three branches in the remote repository currently:
*
master normal delivery branch
After the stable version is released, the code for the stable version branch is merged into the master branch.
* dev daily development branch
The daily development branch, the newly submitted code can pull requests to this branch.
* branch-1.0.0 release version branch
Release version branch, there will be 2.0 ... and other version branches, the version
branch only changes the error, does not add new features.
*
Clone your own warehouse to your local
`git clone https://github.com/analysys/EasyScheduler.git`
*
Add remote repository address, named upstream
`git remote add upstream https://github.com/analysys/EasyScheduler.git`
*
View repository:
`git remote -v`
> There will be two repositories at this time: origin (your own warehouse) and upstream (remote repository)
*
Get/update remote repository code (already the latest code, skip it)
`git fetch upstream`
*
Synchronize remote repository code to local repository
```
git checkout origin/dev
git merge --no-ff upstream/dev
```
If remote branch has a new branch
`DEV-1.0`
, you need to synchronize this branch to the local repository.
```
git checkout -b dev-1.0 upstream/dev-1.0
git push --set-upstream origin dev1.0
```
*
After modifying the code locally, submit it to your own repository:
`git commit -m 'test commit'`
`git push`
*
Submit changes to the remote repository
*
On the github page, click on the new pull request.
<p
align =
"center"
>
<img
src =
"http://geek.analysys.cn/static/upload/221/2019-04-02/90f3abbf-70ef-4334-b8d6-9014c9cf4c7f.png"
width =
"60%"
/>
</
p>
*
Select the modified local branch and the branch to merge past to create a pull request.
<p
align =
"center"
>
<img
src =
"http://geek.analysys.cn/static/upload/221/2019-04-02/fe7eecfe-2720-4736-951b-b3387cf1ae41.png"
width =
"60%"
/>
</
p>
*
Next, the administrator is responsible for
**merging**
to complete the pull request
---
*
首先从远端仓库
*https://github.com/analysys/EasyScheduler.git*
fork一份代码到自己的仓库中
*
远端仓库中目前有三个分支:
...
...
@@ -14,7 +79,7 @@ EasyScheduler提交代码流程
*
把自己仓库clone到本地
`git clone https://github.com/
**
/EasyScheduler.git`
`git clone https://github.com/
analysys
/EasyScheduler.git`
*
添加远端仓库地址,命名为upstream
...
...
@@ -26,17 +91,10 @@ EasyScheduler提交代码流程
> 此时会有两个仓库:origin(自己的仓库)和upstream(远端仓库)
*
获取远端仓库代码(已经是最新代码,就跳过)
*
获取
/更新
远端仓库代码(已经是最新代码,就跳过)
`git fetch upstream `
*
更新远端仓库代码
```
git checkout upstream/dev
git pull upstream dev
```
*
同步远端仓库代码到本地仓库
...
...
@@ -54,7 +112,7 @@ git push --set-upstream origin dev1.0
*
在本地修改代码以后,提交到自己仓库:
`git c
a
-m 'test commit'`
`git c
ommit
-m 'test commit'`
`git push`
*
将修改提交到远端仓库
...
...
@@ -68,6 +126,15 @@ git push --set-upstream origin dev1.0
<p align="center">
<img src="http://geek.analysys.cn/static/upload/221/2019-04-02/fe7eecfe-2720-4736-951b-b3387cf1ae41.png" width="60%" />
</p>
* 接下来由管理员负责将**Merge**完成此次pull request
*
接下来由管理员负责将
**Merge**
完成此次pull request
编辑
预览
Markdown
is supported
0%
请重试
或
添加新附件
.
添加附件
取消
You are about to add
0
people
to the discussion. Proceed with caution.
先完成此消息的编辑!
取消
想要评论请
注册
或
登录