Repository navigation
ci: split code and docs reviews with one Feishu report - #485
Merged
Merged
Conversation
SaladDay
changed the title
SaladDay
marked this pull request as ready for review
October 7, 2026 12:33
This was referenced Oct 7, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Code and documentation reviews run as separate matrix jobs with independent LLM contexts. The docs review checks code/documentation consistency on every PR and checks contradictions, duplicated facts, topic ownership and English/Chinese agreement when documentation changes.
Each job saves its structured result. One notification job waits for both and sends a combined Feishu Card 2.0 through the existing bot webhook. Only the notification job receives webhook credentials. Failed or missing reports are shown as incomplete alongside the other result. A delivery failure is not automatically retried, avoiding duplicate messages. The workflow continues to run after merge with the existing model.
Validation: offline notification tests cover combined single delivery, failed/missing/malformed reports, Feishu error responses, optional signing and ambiguous network failures. All 54 CI utility tests, actionlint 1.7.12, documentation link tests and translation checks pass locally. Actual model execution and bot delivery require the post-merge workflow; no live notification was sent during local verification.