GitHub RAW not updating fast. #171321
-
Select Topic AreaQuestion BodyHi, I was recently making a project that used GitHack CDN to get a TXT file as soon as it is updated via GitHub raw. I updated the file and noticed it wasn't updating on GitHack then I looked at GitHub raw (this issue started like 5 minutes ago) and it hadn't changed and it still hasn't. So I though its because of some of the GitHub workflows may be slowing things down (I am not an expert at GitHub things so this may not make sense) so I tried creating a completely empty repository and putting a file in it called t (no file extension). And I checked it on GitHub raw. Works. Updated it and only now, around 10 minutes later, it has updated. I'm not sure if this is intended and I checked GitHub status and it said it was fine so I was wondering why this is happening and if and how I can solve it. Thank You! Also recently my pages sites have been taking a long time to deploy (i've checked their size and they are like 33Kb). |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 3 replies
-
|
GitHub’s raw file delivery is cached by a CDN, so updates can take a few minutes to show up. That’s why you see a delay even though the repo is updated immediately. There’s nothing wrong with your workflow this is expected behavior. If you need instant updates, you’ll have to serve the file through another host or API that doesn’t rely on CDN caching. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for posting in the GitHub Community, @StuffzEZ! This doesn’t seem to be related to GitHub Pages. Since your question is about delays when accessing files via GitHub RAW (raw.githubusercontent.com), it’s more closely tied to how files are served from repositories (caching/CDN behavior). I’ll go ahead and move this discussion to the |
Beta Was this translation helpful? Give feedback.
GitHub’s raw file delivery is cached by a CDN, so updates can take a few minutes to show up. That’s why you see a delay even though the repo is updated immediately. There’s nothing wrong with your workflow this is expected behavior. If you need instant updates, you’ll have to serve the file through another host or API that doesn’t rely on CDN caching.