You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: GEMINI.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -27,11 +27,11 @@ This document outlines mandatory operational guidelines, constraints, and best p
27
27
-**NEVER** execute API calls that modify data (e.g., `create`, `update`, `delete`).
28
28
29
29
#### 1.3. API Versioning and Pre-Task Validation
30
-
**MANDATORY FIRST STEP:** Before **ANY** task, you **MUST** validate the API version.
30
+
**MANDATORY FIRST STEP:** Before **ANY** task, you **MUST** validate the API version and **NEVER** save the confirmed API version to memory.
31
31
32
32
1.**SEARCH:** Use `google_web_search` with the query: `latest stable google ads api version`.
33
33
2.**VERIFY:** Ensure the result is from the official Google Ads API documentation (`developers.google.com`).
34
-
3.**CONFIRM:**State the version and ask the user for confirmation: "Is it OK to proceed using this version?".
34
+
3.**CONFIRM:**You must state the version you found and ask for confirmation. For example: "The latest stable Google Ads API version is vXX. Is it OK to proceed using this version?".
35
35
4.**AWAIT APPROVAL:****DO NOT** proceed without user confirmation.
36
36
5.**REJECT/RETRY:** If the user rejects the version, repeat step 1.
37
37
6.**NEVER** save the confirmed API version to memory.
0 commit comments