代码拉取完成，页面将自动刷新
You are welcome to submit any bugs, issues and feature requests on this repository.
We have very precise rules over how our git commit messages can be formatted. This leads to more readable messages that are easy to follow when looking through the project history.
Each commit message consists of a header, a body and a footer. The header has a special format that includes a type, a scope and a subject:
<type>(<scope>): <subject>
<BLANK LINE>
<body>
<BLANK LINE>
<footer>
The header with type is mandatory. The scope of the header is optional. This repository has no predefined scopes. A custom scope can be used for clarity if desired.
Any line of the commit message cannot be longer 100 characters! This allows the message to be easier to read on GitHub as well as in various git tools.
The footer should contain a closing reference to an issue if any.
Example 1:
feat: add Fuji release compose files
fix(script): correct run script to use the right ports
Previously device services used wrong port numbers. This commit fixes the port numbers to use the latest port numbers.
Closes: #123, #245, #992
If the commit reverts a previous commit, it should begin with revert: , followed by the header of the reverted commit. In the body it should say: This reverts commit <hash>., where the hash is the SHA of the commit being reverted.
Must be one of the following:
There are no predefined scopes for this repository. A custom scope can be provided for clarity.
The subject contains a succinct description of the change:
Just as in the subject, use the imperative, present tense: "change" not "changed" nor "changes". The body should include the motivation for the change and contrast this with previous behavior.
The footer should contain any information about Breaking Changes and is also the place to reference GitHub issues that this commit Closes.
Breaking Changes should start with the word BREAKING CHANGE: with a space or two newlines. The rest of the commit message is then used for this.
Changes affecting EMQX functionality shall be described in a separate markdown file under changes directory.
File name pattern: changes/(ce|ee)/(feat|perf|fix)-<PR-id>.en.md, where:
ce,ee: Indicates whether given change affects community and enterprise edition (ce), or enterprise edition only (ee); for any change only one file is needed as enterprise edition absorbs all changes from the community edition automatically. When in doubts, one could consult documentation. Enterprise features have a corresponding "Tip" banner, see for example here.feat|perf|fix: Whether the change is a new functionality (feat), performance improvement (perf), or a bug fix (fix).PR-id: Github pull request id. Since pull request id cannot be known before the PR is actually created, it's common to add change log entry in a separate commit.en: ISO 639-1 language code indicating the language the change log entry is written in. Right now we are only accepting entries in English.此处可能存在不合适展示的内容，页面不予展示。您可通过相关编辑功能自查并修改。
如您确认内容无涉及 不当用语 / 纯广告导流 / 暴力 / 低俗色情 / 侵权 / 盗版 / 虚假 / 无价值内容或违法国家有关法律法规的内容，可点击提交进行申诉，我们将尽快为您处理。