README-CN.md (1)

191-202: 确认 Apple SDK 的归类是否正确。

“服务器”列表中包含 Apple SDK，通常 Apple 客户端 SDK 应归于“客户端”。请确认是否应移至“客户端”列表。

如需更正，可将对应条目移动到“客户端”部分并移除“服务器”中的重复。

.github/workflows/issue-triage.md (2)

24-31: Tighten safe-outputs targets to reduce blast radius.

Using target "*" for add-labels/add-comment allows cross-item actions. Prefer “triggering” unless cross-targeting is explicitly required.

   add-labels:
-    max: 100
-    target: "*"
+    max: 100
+    target: "triggering"
   add-comment:
-    max: 10
-    target: "*"
+    max: 10
+    target: "triggering"

---

101-114: Fix Markdown list indentation and capitalization.

Address MD007 and proper noun “Markdown”.

-11. Add an issue comment to the issue with your analysis:
-   - Start with "🎯 Agentic Issue Triage"
-   - Provide a brief summary of the issue
+11. Add an issue comment to the issue with your analysis:
+ - Start with "🎯 Agentic Issue Triage"
+ - Provide a brief summary of the issue
-   - **If duplicate or related issues were found**, add sections listing them with links:
-     - "### 🔗 Potentially Related Issues (this repo)" – bullet list of same-repo issues with titles and links
-     - If applicable: "### 🌐 Cross-repo related issues (org: appwrite)" – bullet list including `owner/repo#number` with titles and links
+ - **If duplicate or related issues were found**, add sections listing them with links:
+   - "### 🔗 Potentially Related Issues (this repo)" – bullet list of same-repo issues with titles and links
+   - If applicable: "### 🌐 Cross-repo related issues (org: appwrite)" – bullet list including `owner/repo#number` with titles and links
  ...
-   - If appropriate break the issue down to sub-tasks and write a checklist of things to do
-   - Use collapsed-by-default sections in the GitHub markdown to keep the comment tidy. Collapse all sections except the short main summary at the top. For bolded section titles, wrap the text with `<strong>` and `</strong>` to make it bold.
+ - If appropriate break the issue down to sub-tasks and write a checklist of things to do
+ - Use collapsed-by-default sections in the GitHub Markdown to keep the comment tidy. Collapse all sections except the short main summary at the top. For bolded section titles, wrap the text with `<strong>` and `</strong>` to make it bold.

.github/workflows/issue-triage.lock.yml (4)

928-932: Label addition scope is too broad.

GH_AW_LABELS_TARGET="*" allows labeling arbitrary items; cap to “triggering” or require explicit allowlist.

-          GH_AW_LABELS_TARGET: "*"
+          GH_AW_LABELS_TARGET: "triggering"

Optionally set GH_AW_LABELS_ALLOWED to a comma-separated allowlist generated from repository labels.

---

539-542: Comment target set to “*”.

Allowing comments on arbitrary targets increases risk; prefer “triggering” unless cross-targeting is required.

-          GH_AW_COMMENT_TARGET: "*"
+          GH_AW_COMMENT_TARGET: "triggering"

---

1241-1256: Secrets requirement may fail on forked PRs.

Hard-failing when COPILOT_* secrets are missing blocks community PR contexts. Consider skip/soft-fail when event is pull_request from a fork.

Example guard:

- if [ -z "$COPILOT_GITHUB_TOKEN" ] && [ -z "$COPILOT_CLI_TOKEN" ]; then
+ if [ -z "$COPILOT_GITHUB_TOKEN" ] && [ -z "$COPILOT_CLI_TOKEN" ]; then
+   if [ "${{ github.event_name }}" = "pull_request" ] && [ "${{ github.event.pull_request.head.repo.fork }}" = "true" ]; then
+     echo "Skipping agent: secrets unavailable on forked PRs"
+     exit 0
+   fi
    echo "Error: Neither COPILOT_GITHUB_TOKEN nor COPILOT_CLI_TOKEN secret is set"
    ...

Edit .md source then recompile.

Also applies to: 4775-4791

---

1272-1273: Safe-outputs config: broadened limits noted. Consider allowlists.

Max add_comment=10 and add_labels=100 are generous. Add an allowlist in config.json (add_labels.allowed) to constrain label names.

-{"add_comment":{"max":10,"target":"*"},"add_labels":{"max":100},"missing_tool":{}}
+{"add_comment":{"max":10,"target":"triggering"},"add_labels":{"max":100,"allowed":["bug","enhancement","documentation"]},"missing_tool":{}}

Also applies to: 2060-2105

README.md (1)

73-101: Confirm the install image tag is the latest 1.8.x.

Hard-coding 1.8.0 may be stale if newer 1.8.x exists. Consider using the latest patch or documenting how to pick it.

#!/bin/bash
# Check available tags for appwrite/appwrite and suggest the highest 1.8.x tag
curl -s 'https://hub.docker.com/v2/repositories/appwrite/appwrite/tags/?page_size=100' \
| jq -r '.results[].name' | grep -E '^1\.8\.[0-9]+$' | sort -V | tail -1

If a newer 1.8.x exists, update the tag in all install snippets accordingly.

Also applies to: 85-91

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Learnt from: stnguyen90
Repo: appwrite/appwrite PR: 10119
File: app/controllers/api/account.php:1226-1232
Timestamp: 2025-07-08T01:20:14.364Z
Learning: In Appwrite, `_APP_DOMAIN` is a required environment variable that must always be set for the system to function properly.