Skip to content

Commit 41cd96d

Browse files
committed
switch the order
Signed-off-by: popcorny <[email protected]>
1 parent 26aab9a commit 41cd96d

File tree

1 file changed

+6
-5
lines changed

1 file changed

+6
-5
lines changed

docs/7-cicd/pr_mr_summary.md

Lines changed: 6 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -7,13 +7,18 @@ When the CI task is executed, it generates a lineage and checks report for your
77
AI Summary leverages state-of-the-art AI agents to understand your changes by analyzing your PR information and updated metadata. It proactively thinks and decides what to validate by data diffing in your data warehouse, then provides comprehensive insights to help you make informed decisions.
88

99
Features
10+
1011
- Automatically identify what to validate
1112
- Explore changes through data diffing in Recce
1213
- Generate actionable insights to guide your merge decision
1314

1415
## How to Use
1516

16-
### 1. Trigger via GitHub PR Comment (GitHub only)
17+
### 1. Trigger via Recce Cloud UI
18+
19+
Go to the Recce Cloud PR/MR session list and click the **"Execute Recce AI Summary"** button to manually trigger the analysis.
20+
21+
### 2. Trigger via GitHub PR Comment (GitHub only)
1722

1823
In your GitHub PR page, simply comment `/recce` to trigger the AI Summary generation. The Recce bot will respond with emoji feedback to show the progress of the analysis.
1924

@@ -25,10 +30,6 @@ In your GitHub PR page, simply comment `/recce` to trigger the AI Summary genera
2530
- 🚀 : Summary is generating
2631
- 👍 : Summary is generated
2732

28-
### 2. Trigger via Recce Cloud UI
29-
30-
Go to the Recce Cloud PR/MR session list and click the **"Execute Recce AI Summary"** button to manually trigger the analysis.
31-
3233
### 3. Trigger via CI Automation (Coming Soon)
3334

3435
AI Summary will be automatically generated by default when you update metadata for your PR through CI, eliminating the need for manual triggering.

0 commit comments

Comments
 (0)