mirror of
https://github.com/kyverno/kyverno.git
synced 2025-03-05 07:26:55 +00:00
remove extra documentation
This commit is contained in:
parent
9885be4050
commit
b001327a25
1 changed files with 0 additions and 22 deletions
|
@ -1,27 +1,5 @@
|
|||
# Contributing to Kyverno
|
||||
|
||||
## Contributing Code
|
||||
|
||||
Unless you are fixing a known bug, we **strongly** recommend discussing it with
|
||||
the core team via a GitHub issue or [in our chat](https://app.slack.com/client/T09NY5SBT/CLGR9BJU9)
|
||||
before getting started to ensure your work is consistent with Kyverno
|
||||
roadmap and architecture.
|
||||
|
||||
All contributions are made via pull request. Note that **all patches from all
|
||||
contributors get reviewed**. After a pull request is made other contributors
|
||||
will offer feedback, and if the patch passes review a maintainer will accept it
|
||||
with a comment. When pull requests fail testing, authors are expected to update
|
||||
their pull requests to address the failures until the tests pass and the pull
|
||||
request merges successfully.
|
||||
|
||||
At least one review from a maintainer is required for all patches (even patches
|
||||
from maintainers).
|
||||
|
||||
Reviewers should leave a "LGTM" comment once they are satisfied with the patch.
|
||||
If the patch was submitted by a maintainer with write access, the pull request
|
||||
should be merged by the submitter after review.
|
||||
|
||||
|
||||
## Code Style
|
||||
|
||||
We follow the community provided standard [code structure](https://github.com/golang-standards/project-layout).
|
||||
|
|
Loading…
Add table
Reference in a new issue