Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
2
22a7f0099
Manage
Activity
Members
Labels
Plan
Issues
0
Issue boards
Milestones
Wiki
Code
Merge requests
0
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Package Registry
Operate
Environments
Terraform modules
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Summer2022
22a7f0099
Commits
8d49a06d
Commit
8d49a06d
authored
5 years ago
by
fangyincheng
Browse files
Options
Downloads
Plain Diff
Merge remote-tracking branch 'upstream/develop' into develop
parents
20aed737
c50891c6
No related branches found
Branches containing commit
No related tags found
Tags containing commit
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
contributing.md
+6
-1
6 additions, 1 deletion
contributing.md
with
6 additions
and
1 deletion
contributing.md
+
6
−
1
View file @
8d49a06d
Contributing to Dubbogo
## 1. Branch
>- The name of branches `SHOULD` be in the format of `feature/xxx`.
>- You `SHOULD` checkout a new branch after a feature branch already being merged into upstream, `DO NOT` commit in the old branch.
...
...
@@ -24,3 +24,8 @@ The title format of the pull request `MUST` follow the following rules:
>- Start with `Dep:` for adding depending libs.
>- Start with `Rem:` for removing feature/struct/function/member/files.
## 3. Code Style
### 3.1 log
> 1 when logging the function's input parameter, you should add '@' before input parameter name.
This diff is collapsed.
Click to expand it.
Preview
0%
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment