代码拉取完成，页面将自动刷新
Contributing to Dubbogo
- The name of branches
SHOULDbe in the format offeature/xxx.- You
SHOULDcheckout a new branch after a feature branch already being merged into upstream,DO NOTcommit in the old branch.
The pr head format is <head> <subject>. The title should be simpler to show your intent.
The title format of the pull request MUST follow the following rules:
- Start with
Doc:for adding/formatting/improving docs.- Start with
Mod:for formatting codes or adding comment.- Start with
Fix:for fixing bug, and its ending should be#issue-idif being relevant to some issue.- Start with
Imp:for improving performance.- Start with
Ftr:for adding a new feature.- Start with
Add:for adding struct function/member.- Start with
Rft:for refactoring codes.- Start with
Tst:for adding tests.- Start with
Dep:for adding depending libs.- Start with
Rem:for removing feature/struct/function/member/files.
Please add a blank line at the end of every file.
Please add a blank line at the sub-title and its content.
Please add s space between the Engilsh word/digit number and the Chinese character.
- 1 when logging the function's input parameter, you should add '@' before input parameter name.
- 1 do not use an underscore in package name, such as
filter_impl.- 2 do not use an underscore in constants, such as
DUBBO_PROTOCOL. use 'DubboProtocol' instead.
- 1 there should be comment for every export func/var.
- 2 the comment should begin with function name/var name.
We dubbogo import blocks should be splited into 3 blocks.
// block 1: the go internal package
import (
"fmt"
)
// block 2: the third package
import (
"github.com/dubbogo/xxx"
"github.com/RoaringBitmap/roaring"
)
// block 3: the dubbo-go package
import (
"dubbo.apache.org/dubbo-go/v3/common"
)
There should be a blank line between the license and the package name.
The package name should not have "xxx_impl".
此处可能存在不合适展示的内容，页面不予展示。您可通过相关编辑功能自查并修改。
如您确认内容无涉及 不当用语 / 纯广告导流 / 暴力 / 低俗色情 / 侵权 / 盗版 / 虚假 / 无价值内容或违法国家有关法律法规的内容，可点击提交进行申诉，我们将尽快为您处理。