From 220c12cc5bccadca6d7edd43ba516b4c3b26c892 Mon Sep 17 00:00:00 2001
From: Coloured-glaze <1044187534@qq.com>
Date: Sat, 7 Jan 2023 00:58:54 +0800
Subject: [PATCH] update

---
 README-en.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/README-en.md b/README-en.md
index 90bc07c..132789f 100644
--- a/README-en.md
+++ b/README-en.md
@@ -1,4 +1,4 @@
-# concurrent map [![Build Status](https://travis-ci.com/orcaman/concurrent-map.svg?branch=master)](https://travis-ci.com/orcaman/concurrent-map)
+# concurrent map [![Build Status](https://travis-ci.com/Coloured-glaze/cmap.svg?branch=master)](https://travis-ci.com/Coloured-glaze/cmap)
 
 As explained [here](http://golang.org/doc/faq#atomic_maps) and [here](http://blog.golang.org/go-maps-in-action), the `map` type in Go doesn't support concurrent reads and writes. `concurrent-map` provides a high-performance solution to this by sharding the map with minimal time spent waiting for locks.