同步操作将从 Gitee 极速下载/Volcano 强制同步,此操作会覆盖自 Fork 仓库以来所做的任何修改,且无法恢复!!!
确定后同步将在后台操作,完成时将刷新页面,请耐心等待。
Please make sure to read and observe our Code of Conduct.
Volcano is a community project driven by its community which strives to promote a healthy, friendly and productive environment. The goal of the community is to develop a volcano system which is useful for runnning high performance workloads such as AI,ML,Deep Learning Application on top of Kubernetes. To build a such volcano system at such scale requires the support of a community with similar aspirations.
We will help you to contribute in different areas like filing issues, developing features, fixing critical bugs and getting your work reviewed and merged.
If you have questions about the development process, feel free to jump into our Slack Channel or join our mailing list.
We are always in need of help, be it fixing documentation, reporting bugs or writing some code. Look at places where you feel best coding practices aren't followed, code refactoring is needed or tests are missing. Here is how you get started.
There are multiple repositories within the Volcano organization. Each repository has beginner-friendly issues that provide a good first issue. For example, Volcano-Issues has help wanted and good first issue labels for issues that should not need deep knowledge of the system. We can help new contributors who wish to work on such issues.
Another good way to contribute is to find a documentation improvement, such as a missing/broken link.
When you are willing to take on an issue, you can assign it to yourself. Just reply with /assign
or /assign @yourself
on an issue,
then the robot will assign the issue to you and your name will present at Assignees
list.
While we encourage everyone to contribute code, it is also appreciated when someone reports an issue. Issues should be filed under the appropriate Volcano sub-repository.
Example: a Volcano issue should be opened to Volcano.
Please follow the prompted submission guidelines while opening an issue.
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:
Pull requests are often called simply "PR". Volcano generally follows the standard github pull request process.
In addition to the above process, a bot will begin applying structured labels to your PR.
The bot may also make some helpful suggestions for commands to run in your PR to facilitate review.
These /command
options can be entered in comments to trigger auto-labeling and notifications.
Refer to its command reference documentation.
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.
scripts: add test codes for metamanager
this add some unit test codes to improve code coverage for metamanager
Fixes #12
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.
此处可能存在不合适展示的内容,页面不予展示。您可通过相关编辑功能自查并修改。
如您确认内容无涉及 不当用语 / 纯广告导流 / 暴力 / 低俗色情 / 侵权 / 盗版 / 虚假 / 无价值内容或违法国家有关法律法规的内容,可点击提交进行申诉,我们将尽快为您处理。