1<!--ts--> 2 * [Automated Sync from the Tensorflow Repository](#automated-sync-from-the-tensorflow-repository) 3 * [Third Party GitHub Actions Used](#third-party-github-actions-used) 4 5<!-- Added by: advaitjain, at: Thu 29 Apr 2021 12:54:23 PM PDT --> 6 7<!--te--> 8 9[TensorFlow repo]: https://github.com/tensorflow/tensorflow 10 11# Continuous Integration System 12 * See the [github workflow files](.github/workflows/ci.yml) for details on 13 exactly what is run as part of the GitHub Actions CI. 14 15 * Tests can also be run from within a docker container: 16 ``` 17 docker build -t tflm-test -f ci/Dockerfile.micro . 18 ``` 19 20 or use the tflm-ci docker image from [here](https://github.com/users/TFLM-bot/packages/container/package/tflm-ci). 21 22 * You will still need to copy or mount your fork of tflite-micro on to this 23 docker container prior to running any tests. 24 25# Automated Sync from the Tensorflow Repository 26 27While TfLite Micro and TfLite are in separate GitHub repositories, the two 28projects continue to share common code. 29 30The [TensorFlow repo][] is the single source of truth for this 31shared code. As a result, any changes to this shared code must be made in the 32[TensorFlow repo][] which will then automatically sync'd via a scheduled 33[GitHub workflow](../.github/workflows/sync.yml). 34 35 36# Third Party GitHub Actions 37We use the following third party actions as part of the TFLM continuous 38integration system. 39 40 * [Create a PR](https://github.com/peter-evans/create-pull-request) to automate 41 sync'ing of shared TfLite and TFLM code. 42 43