test

.github/workflows/generate-coverage-report.yaml

@@ -0,0 +1,12 @@
+name: Create Coverage
+
+on: 
+  push:
+    branches:
+    - main
+
+jobs:
+  generate-coverage-report:
+    uses: eclipse-kanto/kanto/.github/workflows/coverage-template.yaml@main
+    with: 
+      coverage-command: go test ./... -coverprofile=coverage.out -covermode count

README.md

@@ -1,7 +1,9 @@
-![Kanto logo](https://github.com/eclipse-kanto/kanto/raw/main/logo/kanto.svg)
+[![Kanto logo](https://github.com/eclipse-kanto/kanto/raw/main/logo/kanto.svg)](https://eclipse.dev/kanto/)
 
 # Eclipse Kanto - Update Manager
 
+[![Coverage](https://github.com/daniel-milchev/update-manager/wiki/coverage.svg)](#)
+
 The update manager is a component responsible for the orchestration of OTA Updates towards a target device in a smarter way. The general idea is that the update manager receives a desired state specification for the whole target device and it is responsible to take the proper actions so that the current state of the target device matches the desired state.
 
 The desired state comes in a descriptive way, a.k.a desired state manifest. The update manager is designed in such a way that it can easily be modified/extended to support various desired state representation formats.