From c82cfe3615aab9bd231507fc4cce3693609057b5 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Mart=C3=ADn=20Dias?= <tinchodias@gmail.com>
Date: Wed, 13 Apr 2022 03:43:25 -0400
Subject: [PATCH] README: add CI badge

---
 README.md | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/README.md b/README.md
index bc3581d..8a64a9a 100644
--- a/README.md
+++ b/README.md
@@ -1,6 +1,8 @@
 
 # TaskIt
 
+[![Tests](https://github.com/pharo-contributions/taskit/actions/workflows/tests.yml/badge.svg)](https://github.com/pharo-contributions/taskit/actions/workflows/tests.yml)
+
 >Anything that can go wrong, will go wrong. -- Murphy's Law
 
 Expressing and managing concurrent computations is indeed a concern of importance to develop applications that scale. A web application may want to use different processes for each of its incoming requests. Or maybe it wants to use a "thread pool" in some cases. In other case, our desktop application may want to send computations to a worker to not block the UI thread.