What data this category contains
Data for this category originates from code repositories, CI pipelines, linked Issue links, and contributor submission records. Daily generated documents include PR descriptions, code review comments, CI execution results, and merge operation logs. Data updates follow a daily or weekly cycle. Each individual data entry includes fields such as PR number, submitter information, number of changed files, count of review comment entries, CI run status, and merge flag. No additional preset statistical values are included.
Constraints imposed on scheduled tasks and automation
Since data for this category comes from real-time code repository changes and CI pipeline results, scheduled tasks must run during typical low peak times for code submissions to avoid conflicting with CI resource usage. Data updates follow a daily or weekly cycle. Task execution periods should not be too short, to prevent repeated processing of unchanged PR entries. Each data entry includes unstructured review comments and CI logs. Automated processing must adapt to multi-format text parsing rules. Linked Issue links require real-time validity checks. Tasks must include a status check step to avoid processing invalid linked data, ensuring the accuracy of summary results. The most time-consuming steps for this category: confirming change intent and checking test results. Automated tasks must prioritize high-priority PRs to improve overall processing efficiency.
Configuration Settings
This document applies to FastGPT v4.17.0. All following configurations are based on the interface and parameter logic of this version.
| Configuration Item | Recommended Setting | Rationale |
|---|---|---|
| Task Trigger Cycle | Daily 2:00-4:00 AM or every Monday early morning | Matches low peak times for code submissions to avoid occupying CI running resources |
| Maximum Number of PRs Processed Per Run | Top 20 unprocessed PRs | Adapts to per-task resource consumption to prevent task runtime timeouts |
| Review Comment Parsing Threshold | Calibrated based on actual testing | Adapts to differences in review comment formats across teams to ensure parsing accuracy |
| CI Result Check Timeout | 300 seconds | Matches average runtime of typical CI runs to avoid false timeout judgments |
| Invalid Linked Issue Filter Toggle | Enabled | Automatically excludes closed or deleted Issue links to ensure validity of summary data |
| Task Failure Retry Count | 2 times | Addresses temporary code repository API fluctuations to improve task execution success rate |
Three Common Configuration Mistakes
- Phenomenon: Duplicate entries appear in regularly generated PR review summary data. Cause: No PR status filtering rules are configured, leading to repeated processing of already merged or closed PRs.
- Phenomenon: Configured scheduled tasks automatically reset to initial values the next day. Cause: Task configuration is not persisted to storage, and the dependent temporary configuration cache is automatically cleared by the system.
- Phenomenon: Summary data generated after task execution lacks CI result fields. Cause: CI log capture configuration is not enabled, and CI pipeline execution results are not linked.
How to Verify Successful Configuration
- View task scheduling logs to confirm the task starts automatically during the preset trigger period.
- Manually trigger a task, and check that the generated summary data includes correct PR numbers, review comments, and CI run status.
- Test the invalid Issue filter function by using a closed Issue link, confirm the task automatically excludes the entry.
- Check the task failure retry configuration: simulate a code repository API timeout, confirm the task automatically triggers a retry.
The values given are common starting points and should be measured against the reader's own samples.
Question material comes from public community discussions. Configuration values are common starting points and should be measured against your own samples. Verified on 2026-10-19.