PR #12225 from AviaAv: Replaced travis with Github Actions on readme …

…files

CONTRIBUTING.md

@@ -9,7 +9,7 @@ You are welcome to propose and discuss enhancements using project [issues](https
 > The `development` branch is the one where all contributions must be merged before being promoted to master.
 > If you plan to propose a patch, please commit into the `development` branch, or its own feature branch. 
 
-We recommend enabling [travis-ci](https://travis-ci.org/) on your fork of `librealsense` to make sure the changes compile on all platforms and pass unit-tests.
+We recommend enabling [Github Actions](https://docs.github.com/en/actions) on your fork of `librealsense` to make sure the changes compile on all platforms and pass unit-tests.
 
 In addition, please run `pr_check.sh` and `api_check.sh` under `scripts` directory. These scripts verify compliance with project's standards:
 
@@ -69,4 +69,4 @@ For example, when adding new value to [`rs2_option`](https://github.com/IntelRea
 4. The list of Java options used for Android integration - [`wrappers/android/librealsense/src/main/java/com/intel/realsense/librealsense/Option.java`](https://github.com/IntelRealSense/librealsense/blob/v2.32.1/wrappers/android/librealsense/src/main/java/com/intel/realsense/librealsense/Option.java#L4-L64)
 5. The list of options in the [python](https://github.com/IntelRealSense/librealsense/blob/v2.32.1/wrappers/python/pybackend.cpp#L102-L165) wrapper
 
-Once all are updated [travis-ci](https://travis-ci.org/IntelRealSense/librealsense) will give clear indication that each of the wrappers is still passing compilation. 
+Once all are updated [Github Actions](https://docs.github.com/en/actions) will give clear indication that each of the wrappers is still passing compilation. 

unit-tests/readme.md

@@ -23,11 +23,11 @@ This mode of operation lets you test your code on a variety of simulated devices
 ## Test Data
 
 If you would like to run and debug unit-tests locally on your machine but you don't have a RealSense device, we publish a set of *unit-test* recordings. These files capture expected execution of the test-suite over several types of hardware (D415, D435, etc..) 
-Please see [.travis.yml](https://github.com/IntelRealSense/librealsense/blob/master/.travis.yml#L80) and [appveyor.yml](https://github.com/IntelRealSense/librealsense/blob/master/appveyor.yml#L35) for the exact URLs. 
+Please see [Github Actions](https://docs.github.com/en/actions) for the exact URLs. 
 
 > These recordings do not contain any imaging data and therefore can only be useful for unit-tests. If you would like to run your algorithms on top of captured data, please review our [playback and record](https://github.com/IntelRealSense/librealsense/tree/master/src/media) capabilities. 
 
-In addition to running the tests locally, it is very easy to replicate our continuous integration process for your fork of the project - just sign-in to [travis-ci](https://travis-ci.org/) and [AppVeyor](https://ci.appveyor.com/) and enable builds on your fork of `librealsense`. 
+In addition to running the tests locally, it is very easy to replicate our continuous integration process for your fork of the project - just sign-in to [Github Actions](https://docs.github.com/en/actions) and enable builds on your fork of `librealsense`. 
 
 ## Controlling Test Execution