同步操作将从 Gitee 极速下载/KSQL 强制同步,此操作会覆盖自 Fork 仓库以来所做的任何修改,且无法恢复!!!
确定后同步将在后台操作,完成时将刷新页面,请耐心等待。
When submitting a pull request (PR), use the following guidelines:
Fork the confluentinc/ksql repository into your GitHub account: https://github.com/confluentinc/ksql/fork.
Clone your fork of the GitHub repository, replacing <username>
with your GitHub username.
git clone git@github.com:<username>/ksql.git
Add a remote to keep up with upstream changes.
git remote add upstream https://github.com/confluentinc/ksql.git
If you already have a copy, fetch upstream changes.
git fetch upstream
Create a feature branch to work in.
git checkout -b feature-xxx remotes/upstream/master
Work in your feature branch.
git commit -a
Periodically rebase your changes
git pull --rebase
When done, combine ("squash") related commits into a single one
git rebase -i upstream/master
This will open your editor and allow you to re-order commits and merge them:
s
(squash) or f
(fixup) to merge extraneous commits.Submit a pull-request
git push origin feature-xxx
Go to your fork main page
https://github.com/<username>/ksql
If you recently pushed your changes GitHub will automatically pop up a Compare & pull request
button for any branches you recently pushed to. If you click that button it will automatically offer you to submit your pull-request to the confluentinc/ksql
repository.
Addressing code review comments
Repeat steps 5. through 7. to address any code review comments and rebase your changes if necessary.
Push your updated changes to update the pull request
git push origin [--force] feature-xxx
--force
may be necessary to overwrite your existing pull request in case your
commit history was changed when performing the rebase.
Note: Be careful when using --force
since you may lose data if you are not careful.
git push origin --force feature-xxx
Report issues in this GitHub project.
此处可能存在不合适展示的内容,页面不予展示。您可通过相关编辑功能自查并修改。
如您确认内容无涉及 不当用语 / 纯广告导流 / 暴力 / 低俗色情 / 侵权 / 盗版 / 虚假 / 无价值内容或违法国家有关法律法规的内容,可点击提交进行申诉,我们将尽快为您处理。