From 86790bd08375257240fb522faf1af7be89535bd3 Mon Sep 17 00:00:00 2001 From: Rene Jeglinsky Date: Fri, 2 Oct 2026 14:16:45 +0200 Subject: [PATCH 1/6] cleanup file and be more specific wrt consistency check --- .hyperspace/pull_request_bot_review_focus.md | 7 ++----- 1 file changed, 2 insertions(+), 5 deletions(-) diff --git a/.hyperspace/pull_request_bot_review_focus.md b/.hyperspace/pull_request_bot_review_focus.md index 2795475d8..b2dd6e09e 100644 --- a/.hyperspace/pull_request_bot_review_focus.md +++ b/.hyperspace/pull_request_bot_review_focus.md @@ -1,7 +1,4 @@ ---- -description: 'Does a detailed edit on the current file(s).' -tools: ['read', 'agent', 'edit', 'todo', 'search'] ---- +# capire documentation review focus ### ROLE You are a helpful editor for a technical writer. Your task is to review and improve the text while ensuring that it adheres to a structured set of writing rules. All categories are of equal priority—no rule should be prioritized over another. @@ -72,7 +69,7 @@ Focus on content-level accessibility based on WCAG guidelines. Prioritize Level - Make sure that sentences are complete and that images, code blocks, and so on are not in between overflowing sentences. 7. Consistency -Use the `search` tool to check consistency across the repo. Report findings but do not auto-fix — flag locations for the author to review. +Check consistency across the repo. Report findings but do not auto-fix — flag locations for the author to review. Identify the questionable changes and search through the repository or an cap.cloud.sap. - **Terminology**: Identify terms, product names, or UI labels introduced or changed in the diff. Search the repo for prior uses of the old term and flag files where the wording may be inconsistent or outdated. - **Renamed identifiers**: When a variable, class, method, config key, or file is renamed in the diff, search the repo for references to the old name and list any files that likely need updating. From 169c6162956100bd6598cef49d151bac1807c1fd Mon Sep 17 00:00:00 2001 From: Rene Jeglinsky Date: Fri, 2 Oct 2026 14:16:57 +0200 Subject: [PATCH 2/6] rename runtime scope --- java/change-tracking.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/java/change-tracking.md b/java/change-tracking.md index 4aec34bfe..4b44eb919 100644 --- a/java/change-tracking.md +++ b/java/change-tracking.md @@ -24,7 +24,7 @@ To use the change tracking feature, you need to add a dependency to [cds-feature com.sap.cds cds-feature-change-tracking - runtime + run ``` From d5c35fc75d09f6a867b4985076bdd5492ee98b2f Mon Sep 17 00:00:00 2001 From: Rene Jeglinsky Date: Fri, 2 Oct 2026 14:20:08 +0200 Subject: [PATCH 3/6] Revert "rename runtime scope" This reverts commit 169c6162956100bd6598cef49d151bac1807c1fd. --- java/change-tracking.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/java/change-tracking.md b/java/change-tracking.md index 4b44eb919..4aec34bfe 100644 --- a/java/change-tracking.md +++ b/java/change-tracking.md @@ -24,7 +24,7 @@ To use the change tracking feature, you need to add a dependency to [cds-feature com.sap.cds cds-feature-change-tracking - run + runtime ``` From 0e96676d9f05b731ec8e4375efc3bdeabf65473e Mon Sep 17 00:00:00 2001 From: Rene Jeglinsky Date: Fri, 2 Oct 2026 14:25:47 +0200 Subject: [PATCH 4/6] rename config property --- guides/deploy/build.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/guides/deploy/build.md b/guides/deploy/build.md index bc85e7304..dac6f2ed1 100644 --- a/guides/deploy/build.md +++ b/guides/deploy/build.md @@ -117,7 +117,7 @@ To change the default target folder, use the cds.build.target=pa #### Node.js Node.js projects use the folder _./gen_ below the project root as build target folder by default.
-Relevant source files from _db_ or _srv_ folders are copied into this folder, which makes it self-contained and ready for deployment. The default folder names can be changed with the cds.folders.db, cds.folders.srv, cds.folders.app configuration. Or you can go for individual build task configuration for full flexibility. +Relevant source files from _db_ or _srv_ folders are copied into this folder, which makes it self-contained and ready for deployment. The default folder names can be changed with the cds.folders.database, cds.folders.srv, cds.folders.app configuration. Or you can go for individual build task configuration for full flexibility. Project files like _.cdsrc.json_ or _.npmrc_ located in the _root_ folder or in the _srv_ folder of your project are copied into the application's deployment folder (default _gen/srv_). Files located in the _srv_ folder have precedence over the corresponding files located in the project root directory. As a consequence these files are used when deployed to production. Make sure that the folders do not contain one of these files by mistake. Consider using profiles `development` or `production` in order to distinguish environments. CDS configuration that should be kept locally can be defined in a file _.cdsrc-private.json_. From 3dfff75ea2089d52e29abb5024ef7dfd81534474 Mon Sep 17 00:00:00 2001 From: Rene Jeglinsky Date: Fri, 2 Oct 2026 14:28:42 +0200 Subject: [PATCH 5/6] Revert "rename config property" This reverts commit 0e96676d9f05b731ec8e4375efc3bdeabf65473e. --- guides/deploy/build.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/guides/deploy/build.md b/guides/deploy/build.md index dac6f2ed1..bc85e7304 100644 --- a/guides/deploy/build.md +++ b/guides/deploy/build.md @@ -117,7 +117,7 @@ To change the default target folder, use the cds.build.target=pa #### Node.js Node.js projects use the folder _./gen_ below the project root as build target folder by default.
-Relevant source files from _db_ or _srv_ folders are copied into this folder, which makes it self-contained and ready for deployment. The default folder names can be changed with the cds.folders.database, cds.folders.srv, cds.folders.app configuration. Or you can go for individual build task configuration for full flexibility. +Relevant source files from _db_ or _srv_ folders are copied into this folder, which makes it self-contained and ready for deployment. The default folder names can be changed with the cds.folders.db, cds.folders.srv, cds.folders.app configuration. Or you can go for individual build task configuration for full flexibility. Project files like _.cdsrc.json_ or _.npmrc_ located in the _root_ folder or in the _srv_ folder of your project are copied into the application's deployment folder (default _gen/srv_). Files located in the _srv_ folder have precedence over the corresponding files located in the project root directory. As a consequence these files are used when deployed to production. Make sure that the folders do not contain one of these files by mistake. Consider using profiles `development` or `production` in order to distinguish environments. CDS configuration that should be kept locally can be defined in a file _.cdsrc-private.json_. From 8266b03242e31cb4fc49e518df29b4ae1e7a309f Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Ren=C3=A9=20Jeglinsky?= Date: Fri, 2 Oct 2026 14:34:47 +0200 Subject: [PATCH 6/6] Update .hyperspace/pull_request_bot_review_focus.md Co-authored-by: hyperspace-pr-bot[bot] <209611008+hyperspace-pr-bot[bot]@users.noreply.github.com> --- .hyperspace/pull_request_bot_review_focus.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.hyperspace/pull_request_bot_review_focus.md b/.hyperspace/pull_request_bot_review_focus.md index b2dd6e09e..694407b66 100644 --- a/.hyperspace/pull_request_bot_review_focus.md +++ b/.hyperspace/pull_request_bot_review_focus.md @@ -69,7 +69,7 @@ Focus on content-level accessibility based on WCAG guidelines. Prioritize Level - Make sure that sentences are complete and that images, code blocks, and so on are not in between overflowing sentences. 7. Consistency -Check consistency across the repo. Report findings but do not auto-fix — flag locations for the author to review. Identify the questionable changes and search through the repository or an cap.cloud.sap. +Check consistency across the repo. Report findings but do not auto-fix — flag locations for the author to review. Identify questionable changes, and search the repository or cap.cloud.sap for related terms and references. - **Terminology**: Identify terms, product names, or UI labels introduced or changed in the diff. Search the repo for prior uses of the old term and flag files where the wording may be inconsistent or outdated. - **Renamed identifiers**: When a variable, class, method, config key, or file is renamed in the diff, search the repo for references to the old name and list any files that likely need updating.