20 lines
838 B
ReStructuredText
20 lines
838 B
ReStructuredText
|
Contributions to validations-common follow guidelines largely similar
|
||
|
|
to those of other openstack projects.
|
||
|
|
|
||
|
|
If you're interested in contributing to the validations-libs project,
|
||
|
|
the following will help get you started:
|
||
|
|
|
||
|
|
https://docs.openstack.org/infra/manual/developers.html
|
||
|
|
|
||
|
|
If you already have a good understanding of how the system works and your
|
||
|
|
OpenStack accounts are set up, you can skip to the development workflow
|
||
|
|
section of this documentation to learn how changes to OpenStack should be
|
||
|
|
submitted for review via the Gerrit tool:
|
||
|
|
|
||
|
|
https://docs.openstack.org/infra/manual/developers.html#development-workflow
|
||
|
|
|
||
|
|
Pull requests submitted through GitHub will be ignored.
|
||
|
|
|
||
|
|
Validations are meant to verify functionality of tripleo systems.
|
||
|
|
Therefore a special care should be given to testing your code before submitting a review.
|