Repository navigation
fix: correct blog and news metadata - #1147
Merged
dengliming merged 3 commits intoOct 10, 2026
Merged
Conversation
Contributor
Author
|
The fixes for #1136 are implemented, and local production builds passed for both English and Chinese. The GitHub Actions runs are currently marked |
This was referenced Oct 1, 2026
Member
|
@anbv29 Please resolve the conflict. |
Contributor
Author
|
Hi @dengliming the merge conflicts with main are resolved now. Please review and merge when you have a moment. Thanks! |
dengliming
approved these changes
Oct 10, 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
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.
Summary
Verification
Notes
The Markdown audit still identifies a pre-existing table-alignment warning in
blog/SPI-SourceCode-Analysis-PredicateJudge-SPI.md. The affected table line was not changed by this pull request.Closes #1136