Follow us at@VMWEventBroker
Follow us atvcenter-event-broker-appliance
Join us at#vcenter-event-broker-appliance
Email us at[email protected]
The VMware Event Broker Appliance team welcomes contributions from the community and this page presents the guidelines for contributing to VMware Event Broker Appliance.
Following the guidelines helps to make the contribution process easy, collaborative, and productive.
Before you start working with the VMware Event Broker Appliance, please read our Developer Certificate of Origin. All contributions to this repository must be signed as described on that page. Your signature certifies that you wrote the patch or have the right to pass it on as an open-source patch.
This is a rough outline of what a contributor’s workflow looks like:
See below for details on commit best practices
and supported prefixes, e.g.
Note: If you are new to Git(hub) check out Git rebase, squash…oh my! for more details on how to successfully contribute to an open source project.
Please submit bug reports and feature requests by using our GitHub Issues page.
Before you submit a bug report about the code in the repository, please check the Issues page to see whether someone has already reported the problem. In the bug report, be as specific as possible about the error and the conditions under which it occurred. On what version and build did it occur? What are the steps to reproduce the bug?
Feature requests should fall within the scope of the project.
Before submitting a pull request, please make sure that your change satisfies the following requirements:
We follow the conventions described in How to Write a Git Commit Message.
Be sure to include any related GitHub issue references in the commit message,
CHANGELOG.md and release page use commit message prefixes for grouping
and highlighting. A commit message that starts with
[prefix:] will place this
commit under the respective section in the
The following example creates a commit referencing the
issue: 1234 and puts
the commit message in the
git commit -s -m "feat: Add Slack Example" -m "Closes: #1234"
Currently the following prefixes are used:
fix:- Use for bug fixes
feat:- A new feature
chore:- Use for repository related activities
docs:- Use for changes to the documentation
If your contribution falls into multiple categories, e.g.
fix it is
recommended to break up your commits using distinct prefixes.
Get started quickly with your contributions with our getting started guide
rainpole.io is released as open source software and provides community support through our GitHub project page. If you encounter an issue or have a question, feel free to reach out on the GitHub issues page for rainpole.io.
Our team welcomes contributions from the community!