Please make sure to read and observe our Code of Conduct.
We will help you to contribute in different areas like filing issues, developing features, fixing bugs and getting your work reviewed and merged.
Please do not ever hesitate to ask a question or send a pull request.
This is a rough outline of what a contributor's workflow looks like:
FabEdge generally follows the standard github pull request process.
To make it easier for your PR to receive reviews, consider the reviewers will need you to:
We follow a rough convention for commit messages that is designed to answer two questions: what changed and why. The subject line should feature the what and the body of the commit should describe the why.
agent: add test codes for manager
this add some unit test codes to improve code coverage for agent
Fixes #666
The format can be described more formally as follows:
<subsystem>: <what changed>
<BLANK LINE>
<why this change was made>
<BLANK LINE>
<footer>
The first line is the subject and should be no longer than 70 characters, the second line is always blank, and other lines should be wrapped at 80 characters. This allows the message to be easier to read on GitHub as well as in various git tools.
Note: if your pull request isn't getting enough attention, you can use the reach out on Slack to get help finding reviewers.
There are multiple types of tests. The location of the test code varies with type, as do the specifics of the environment needed to successfully run the test:
Continuous integration will run these tests on PRs.
此处可能存在不合适展示的内容,页面不予展示。您可通过相关编辑功能自查并修改。
如您确认内容无涉及 不当用语 / 纯广告导流 / 暴力 / 低俗色情 / 侵权 / 盗版 / 虚假 / 无价值内容或违法国家有关法律法规的内容,可点击提交进行申诉,我们将尽快为您处理。