From 9667e070c5d130dc7033b222fd8bf5dc77ed65ef Mon Sep 17 00:00:00 2001
From: peaklabs-dev <122374094+peaklabs-dev@users.noreply.github.com>
Date: Mon, 9 Nov 2026 00:34:27 +0100
Subject: [PATCH] docs(agents): link only issues in change files

---
 AGENTS.md | 1 +
 1 file changed, 1 insertion(+)

diff --git a/AGENTS.md b/AGENTS.md
index bf8bb0f009..62df0e509c 100644
--- a/AGENTS.md
+++ b/AGENTS.md
@@ -335,6 +335,7 @@ The summary reads as one sentence with the heading of its section, never in the
 
 - Start with a capital letter or a code span, and end without a period. A reason follows after a comma.
 - Write for the person who runs Coolify. Name the page, setting, or API field that changes, not the class or the file.
+- Link the issues that a change fixes or closes at the end of the summary, for example `([#1234](https://github.com/coollabsio/coolify/issues/1234))`. Do not link pull requests.
 - Do not use bold. Put each UI name, such as a page, tab, button, setting, or label, in its own code span, for example `Advanced` > `Deployment`.
 - Do not put exploit details, payloads, or unreleased advisory IDs in a change file.