diff --git a/README.md b/README.md
index 868527096943d..4f23c3a260b96 100644
--- a/README.md
+++ b/README.md
@@ -31,11 +31,18 @@ You are encouraged to check out other Kafka projects from LinkedIn:
 * [Kafka Monitor](https://github.com/linkedin/kafka-monitor)
 
 ### CI ###
-We are currently using Travis as the CI framework, and the testing results can be found [here](https://travis-ci.com/github/linkedin/kafka)
+We are currently using Github Actions as the CI framework, and the testing results can be found [here](https://github.com/linkedin/kafka/actions).
 To publish a release, go to [the release page](https://github.com/linkedin/kafka/releases) and manually create a new release.
-Once the release tag is created, a Travis job will be triggered to run the necessary tests. And once the test passes, the artifacts
+Once the release tag is created, a test job will be triggered to run the necessary tests. And once the test passes, the artifacts
 will be published to [the bintray hosting LinkedIn projects](https://dl.bintray.com/linkedin/maven/com/linkedin/kafka/kafka_2.12/).
 
+Currently we've configured the CI flow to run only unit tests for 'clients' and 'core' when a pull request is created or updated:
+    ./gradlew :clients:unitTest :core:unitTest
+In contrast, all tests for `cliests' and `core' are run when creating a release, which may be significantly longer than running the unit tests:
+    ./gradlew :clients:test :core:test
+The reason for this mixed approach is to get faster feedback from CI during code reviews
+and still gain the more through test coverage when publishing a release.
+
 ### Contributing ###
 
 At this moment we are not accepting external contributions directly. Please