Git 贡献提交规范一

仓库贡献规范二

如果您在使用过程中遇到任何问题，或者想提出任何建议，请在 **仓库上新建您的 Issue。在新建 Issue 时，请先搜索 Issue，以确保您的问题没有被提出过。新建 Issue 时，请参考对应类型的模板。

欢迎各位开发者提交代码共同建设 ***。您可以 Fork ** 仓库到您自己名下，然后推送一个 MR 到 ** 项目下，MR 将在 CI 流水线通过和管理员 Review 之后合入主干。

when func is end, we need to stop timer.

when func is end, we need to stop timer.

Mention if this PR is part of any design or a continuation of previous PRs

Fixes #
PR Title follows the convention of <type>(<scope>): <subject>
Has the change log section been updated?
Commit has unit tests
Commit has integration tests
(Optional) Are upgrade changes included in this PR? If not, mention the issue/PR to track:
(Optional) If documentation changes are required, which issue on https://github.com/openebs/website is used to track them: PLEASE REMOVE BELOW INFORMATION BEFORE SUBMITTING

The PR title message must follow convention: <type>(<scope>): <subject>.

Where:

type is defining if release will be triggering after merging submitted changes, details in CONTRIBUTING.md. Most common types are:
- feat - for new features, not a new feature for build script
- fix - for bug fixes or improvements, not a fix for build script
- chore - changes not related to production code
- docs - changes related to documentation
- style - formatting, missing semi colons, linting fix etc; no significant production code changes
- test - adding missing tests, refactoring tests; no production code change
- refactor - refactoring production code, eg. renaming a variable or function name, there should not be any significant production code changes
scope is a single word that best describes where the changes fit. Most common scopes are like:
- data engine (localpv, jiva, cstor)
- feature (provisioning, backup, restore, exporter)
- code component (api, webhook, cast, upgrade)
- test (tests, bdd)
- chores (version, build, log, travis)
subject is a single line brief description of the changes made in the pull request.

您可以通过以下渠道联系我们：

参照模板：AimRT