[flink-kubernetes-operator] 03/03: [FLINK-26142] Add CI/CD section in README

[gy...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

gyfora pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/flink-kubernetes-operator.git

commit e113440c496a9f02f891c9b05f9bf1fc3506a1f9
Author: wangyang0918 <da...@alibaba-inc.com>
AuthorDate: Thu Feb 17 18:06:37 2022 +0800

    [FLINK-26142] Add CI/CD section in README
    
    Closes #4
---
 README.md | 9 +++++++++
 1 file changed, 9 insertions(+)

diff --git a/README.md b/README.md
index 249aa9a..26dd8fc 100644
--- a/README.md
+++ b/README.md
@@ -68,3 +68,12 @@ cat /opt/flink/conf/flink-conf.yaml
 rest.port: 8081
 rest.address: localhost
 ```
+### CI/CD
+[GitHub Actions](https://help.github.com/en/actions/getting-started-with-github-actions/about-github-actions) help you automate your software development workflows in the same place you store code and collaborate on pull requests and issues.
+You can write individual tasks, called actions, and combine them to create a custom workflow.
+Workflows are custom automated processes that you can set up in your repository to build, test, package, release, or deploy any code project on GitHub.
+
+Considering the cost of running the builds, the stability, and the maintainability, flink-kubernetes-operator chose GitHub Actions and build the whole CI/CD solution on it.
+All the unit tests, integration tests, and the end-to-end tests will be triggered for each PR.
+
+Note: Please make sure the CI passed before merging.