Please make sure the bug is not already reported by searching the repository with reasonable keywords. Then, open an issue with steps to reproduce.
Recommend the standard GitHub flow based on forking and pull requests.
The following diagram and practice steps show the basic process of contributing code to CubeFS:
$ git remote add me https://github.com/your/cubefs
)$ git checkout master && git pull
)$ git branch your-branch && git checkout your-branch
)$ git commit -s && git push me
)your/cubefs:your-branch
into cubefs/cubefs:master
)Note 1:
The DOC Check is enabled and required. Please make sign your commit by using -s
argument to add a valid Signed-off-by
line at bottom of your commit message.
Example:
$ git commit -s
Note 2:
If your pull request solves an existing issue or implements a feature request with an existing issue.
Please use the fixes keyword in the pull request to associate the pull request with the relevant issue.
Note 3:
Every pull request that merges code to the master branch needs to be approved by at least one core maintainer for code review and pass all checks (including the DCO check) before it can be merged.
go fmt
or gofumpt
before submitting it.Example:
For example, the author information must match the Signed-off-by information.
Author: users <users@cubefs.groups.io>
Date: Thu Apr 27 09:40:02 2023 +0800
feat(cubefs): this is an example
close: #1
Signed-off-by: users <users@cubefs.groups.io>
此处可能存在不合适展示的内容,页面不予展示。您可通过相关编辑功能自查并修改。
如您确认内容无涉及 不当用语 / 纯广告导流 / 暴力 / 低俗色情 / 侵权 / 盗版 / 虚假 / 无价值内容或违法国家有关法律法规的内容,可点击提交进行申诉,我们将尽快为您处理。