From 2ce8788487e2c28663c6bb67f195ffd6c6756f91 Mon Sep 17 00:00:00 2001
From: Oscar Zhou <100548325+oscarzhou-portainer@users.noreply.github.com>
Date: Sat, 23 Aug 2025 10:56:04 +1200
Subject: [PATCH] fix(autoupdate): update tooltips in edge stack gitops update 
 [BE-12177] (#1084)

---
 .../AutoUpdateFieldset/AutoUpdateSettings.tsx | 19 +++++++++++++++++--
 1 file changed, 17 insertions(+), 2 deletions(-)

diff --git a/app/react/portainer/gitops/AutoUpdateFieldset/AutoUpdateSettings.tsx b/app/react/portainer/gitops/AutoUpdateFieldset/AutoUpdateSettings.tsx
index 48b40a642..bbdc64f77 100644
--- a/app/react/portainer/gitops/AutoUpdateFieldset/AutoUpdateSettings.tsx
+++ b/app/react/portainer/gitops/AutoUpdateFieldset/AutoUpdateSettings.tsx
@@ -77,7 +77,7 @@ export function AutoUpdateSettings({
               checked={value.ForcePullImage || false}
               label="Re-pull image"
               labelClass="col-sm-3 col-lg-2"
-              tooltip="If enabled, then when redeploy is triggered via the webhook or polling, if there's a newer image with the tag that you've specified (e.g. changeable development builds), it's pulled and redeployed. If you haven't specified a tag, or have specified 'latest' as the tag, then the image with the tag 'latest' is pulled and redeployed."
+              tooltip="If enabled, then when redeploy is triggered via the webhook or polling, if there's a newer image with the tag that you've specified (e.g. changeable development builds), it's pulled and redeployed. If you haven't specified a tag, or have specified 'latest' as the tag, then the image with the tag 'latest' is pulled and redeployed. With relative path enabled, it also redeploys when mounted files (not just the compose file) change."
               onChange={(value) => onChange({ ForcePullImage: value })}
             />
           </div>
@@ -107,7 +107,22 @@ export function AutoUpdateSettings({
                 the cluster being overwritten.
               </p>
             </>
-          ) : undefined
+          ) : (
+            <p>
+              If enabled, then when redeploy is triggered via the webhook or
+              polling, the stack behavior depends on the stack type:
+              <br />
+              <strong>Regular stacks:</strong> Redeploy whenever triggered,
+              without checking for docker-compose file changes
+              <br />
+              <strong>Edge stacks:</strong> Redeploy only when the
+              docker-compose file in the Git repository has changed. Commits
+              that change unrelated files or mounted files (via relative paths)
+              do not trigger redeployment. Currently, this option does not
+              change the redeployment behavior, and it remains a temporary
+              solution until a more complete behavior is added later.
+            </p>
+          )
         }
       />
     </>