From 4ae88de943fe56fb5cfe05549cfeb8c2c71124c5 Mon Sep 17 00:00:00 2001
From: FarisZR <35614734+FarisZR@users.noreply.github.com>
Date: Wed, 31 May 2023 03:58:48 +0300
Subject: [PATCH] update readme details

---
 README.md | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/README.md b/README.md
index 51f9984..9112461 100644
--- a/README.md
+++ b/README.md
@@ -1,6 +1,6 @@
 # caddy-dns-OCI
 I created this project to avoid having to manually update my custom caddy images.
-It checks for updates every hour and rebuilds the images accordingly.
+It checks for updates 4 times a day (every 6 hours) and rebuilds the images accordingly.
 
 ## Which plugins are supported?
 Pretty much all plugins except lego-deprecated and plugins affected by https://github.com/FarisZR/caddy-dns-OCI/issues/1 or https://github.com/FarisZR/caddy-dns-OCI/issues/2
@@ -62,6 +62,8 @@ The [start-build.yml](.github/workflows/start-build.yml) requires the following
 then it calls [build-image.yml](.github/workflows/build-image.yml) using those inputs twice, once for the normal image and once for alpine.
 and if the default build succeeds, it triggers the final job, `update-plugin-build-commit', which does what it says and updates the build hash for that plugin in [git-hashes](/git-hashes/).
 
+Each start-build.yml run uses the plugins name as a concurrency group, to stop multiple builds for the same plugin from running at the same time, without stopping builds from different checks for different plugins from continuing.
+
 ## Contribute 
 Thanks for your interest! as long as the project doesn't hit github's 256 job limit, it should be fine.