From 5d15cb81f9d29ec0c99fc7a9f52fabd10598b971 Mon Sep 17 00:00:00 2001
From: Stanley Goldman <Stanley.Goldman@gmail.com>
Date: Thu, 12 Apr 2018 10:37:11 -0400
Subject: [PATCH] Calling CacheHasBeenInvalidated instead of RefreshCache

At this point we know these values have already been marked as invalid.
There is no reason to call RefreshCache on them and go through that
pipeline again. Furthermore that pipeline is currently waiting for valid
data, so it will not fire off the invalidation events a second time.
---
 src/GitHub.Api/Git/Repository.cs | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/GitHub.Api/Git/Repository.cs b/src/GitHub.Api/Git/Repository.cs
index 4101e5caa..b5e4d7da7 100644
--- a/src/GitHub.Api/Git/Repository.cs
+++ b/src/GitHub.Api/Git/Repository.cs
@@ -92,7 +92,7 @@ public void Start()
         {
             foreach (var cacheType in cacheInvalidationRequests)
             {
-                RefreshCache(cacheType);
+                CacheHasBeenInvalidated(cacheType);
             }
         }